Re: kernel module
2010/1/9 Luca : > Hi all, > I created a kernel module which can be passed some command line arguments > (I tried that with insmod and it works). > > Now I would like, when I start the kernel with grub, to have this module > loaded at boot time so I can pass, at boot time, a kernel boot option to it. > I think this usually happens in a modules configuration file. Something like this? "https://fedoraproject.org/wiki/KernelCommonProblems#How_to_set_module_options_for_boot_drivers"; -c -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
kernel module
Hi all, I created a kernel module which can be passed some command line arguments (I tried that with insmod and it works). Now I would like, when I start the kernel with grub, to have this module loaded at boot time so I can pass, at boot time, a kernel boot option to it. I mean having something like kernel vmlinuz root=/dev/ram0 initrd=linuxrc mymodule.param1="myparamvalue" initrd is it possible? Thanks, Luca -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Kernel boot problems or is my hard drive failing ?
2010/1/6 Linuxguy123 : > If I power down my laptop via the usual KStart->Shutdown means, it can > take up to 4 restart attempts before it fully boots. > > It has no problem launching grub and the kernel selection screen. That > it does reliably every time. After that, there are issues. Just a wild stab in the dark, but you don't have a USB drive or memory stick plugged in while trying to boot, do you? -c -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Kernel boot problems or is my hard drive failing ?
> If I power down my laptop via the usual KStart->Shutdown means, it can > take up to 4 restart attempts before it fully boots. That sounds like wonky hardware > It has no problem launching grub and the kernel selection screen. That > it does reliably every time. After that, there are issues. If it launches grub the disk is fine (Grub is loaded off the disk) and I assume the laptop has one disk. > Twice I will get a back screen with a flashing cursor. Then I will get > an ehci -19 error. Then it will boot properly. The EHCI error is from USB so perhaps points to a USB problem. > Is anyone else experiencing a problem booting ? Does this sound like a > kernel problem or is my hard drive failing ? If a soft reboot fails but a hard reboot (reset button held down) works I'd suspect its something hardware related not getting properly shutdown/restarting etc. For diagnostics boot with "verbose norhgb" that should spew lots of messages and not hide it all with the graphical stuff - meaning you can actually see what is going on. See where that hangs. You could also see if reboot=acpi helps. That changes the way the reboot is done and might be better for modern machines. Len Brown is currently collecting data on making this a default so your box may be a useful data point. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Kernel boot problems or is my hard drive failing ?
On 01/06/2010 10:35 AM, Linuxguy123 wrote: > On Wed, 2010-01-06 at 09:23 +1100, Chris Smart wrote: >> 2010/1/6 Linuxguy123 : >>> >>> Is anyone else experiencing a problem booting ? Does this sound like a >>> kernel problem or is my hard drive failing ? >> >> If your drive and BIOS supports S.M.A.R.T, then gnome-disk-utility >> (palimpsest) will tell you the status of your drive.. > > I can't seem to find this utility in Fedora. Can someone verify its > spelling/existence ? yum search palimpsest > Thanks -- Kevin J. Cummings kjch...@rcn.com cummi...@kjchome.homeip.net cummi...@kjc386.framingham.ma.us Registered Linux User #1232 (http://counter.li.org) -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Kernel boot problems or is my hard drive failing ?
On Wed, 2010-01-06 at 16:48 +0100, Michael Schwendt wrote: > On Wed, 06 Jan 2010 08:35:43 -0700, Linuxguy123 wrote: > > > On Wed, 2010-01-06 at 09:23 +1100, Chris Smart wrote: > > > 2010/1/6 Linuxguy123 : > > > > > > > > Is anyone else experiencing a problem booting ? Does this sound like a > > > > kernel problem or is my hard drive failing ? > > > > > > If your drive and BIOS supports S.M.A.R.T, then gnome-disk-utility > > > (palimpsest) will tell you the status of your drive.. > > > > I can't seem to find this utility in Fedora. Can someone verify its > > spelling/existence ? > > You can, too: yum search palim Found it and installed it. Its a very useful application. It was part of the gnome-disk-utility package. I missed that part in the op. My disk is SMART enabled and the utility reports that it is healthy. I have a booting problem to look into. Thanks for the help. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Kernel boot problems or is my hard drive failing ?
Around 03:35pm on Wednesday, January 06, 2010 (UK time), Linuxguy123 scrawled: > On Wed, 2010-01-06 at 09:23 +1100, Chris Smart wrote: > > 2010/1/6 Linuxguy123 : > > > > > > Is anyone else experiencing a problem booting ? Does this sound like a > > > kernel problem or is my hard drive failing ? > > > > If your drive and BIOS supports S.M.A.R.T, then gnome-disk-utility > > (palimpsest) will tell you the status of your drive.. > > I can't seem to find this utility in Fedora. Can someone verify its > spelling/existence ? Its a gui utility. $ palimpsest gnome-disk-utility is the package name. $ yum provides */palimpsest Loaded plugins: presto, refresh-packagekit updates/filelists_db | 4.7 MB 01:56 gnome-disk-utility-2.28.1-1.fc12.x86_64 : Disk management application Repo: fedora Matched from: Filename: /usr/share/gnome/help/palimpsest Filename: /usr/share/omf/palimpsest Filename: /usr/bin/palimpsest gnome-disk-utility-2.28.1-1.fc12.x86_64 : Disk management application Repo: installed Matched from: Filename: /usr/bin/palimpsest Steve -- (o< www.stevesearle.com //\ Powered by Fedora V_/_No MS products were used in the creation of this message 15:54:58 up 32 days, 15:21, 1 user, load average: 0.02, 0.05, 0.06 pgpKcXUWkYJM4.pgp Description: PGP signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Kernel boot problems or is my hard drive failing ?
On Wed, 06 Jan 2010 08:35:43 -0700, Linuxguy123 wrote: > On Wed, 2010-01-06 at 09:23 +1100, Chris Smart wrote: > > 2010/1/6 Linuxguy123 : > > > > > > Is anyone else experiencing a problem booting ? Does this sound like a > > > kernel problem or is my hard drive failing ? > > > > If your drive and BIOS supports S.M.A.R.T, then gnome-disk-utility > > (palimpsest) will tell you the status of your drive.. > > I can't seem to find this utility in Fedora. Can someone verify its > spelling/existence ? You can, too: yum search palim -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Kernel boot problems or is my hard drive failing ?
On Wed, 2010-01-06 at 09:23 +1100, Chris Smart wrote: > 2010/1/6 Linuxguy123 : > > > > Is anyone else experiencing a problem booting ? Does this sound like a > > kernel problem or is my hard drive failing ? > > If your drive and BIOS supports S.M.A.R.T, then gnome-disk-utility > (palimpsest) will tell you the status of your drive.. I can't seem to find this utility in Fedora. Can someone verify its spelling/existence ? Thanks -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Kernel boot problems or is my hard drive failing ?
>> Is anyone else experiencing a problem booting ? Does this sound like a >> kernel problem or is my hard drive failing ? >From the error message, possibly there is a problem with your SATA controller, or with your SATA cables. SATA cables are pretty cheap. Get some new ones and replace them all. If that doesn't fix your problem, while SATA controllers aren't as cheap as cables, they are at least affordable. Buy a new SATA controller, install it and attach your drive to it. If your old SATA controller is removable (ie not integrated with the motherboard), then also remove it. And what the other guy said - check your drive health with S.M.A.R.T. Also, all the drive manufacturers offer free downloads of drive testing utilities. These are image files that generate boot floppies or CD-ROMs. Download the utility for your drive, make the boot disk, boot off it, and run the non-destructive tests. This can be valuable because vendors often add proprietary test code, that only their own diagnostic tools know how to run. There is a possibility that this will detect a drive failure that S.M.A.R.T. may not yet know about. But First... BACK UP ALL YOUR DATA! RIGHT NOW! There is a clock ticking, you see. Can you hear it? "Tick, Tick, Tick." Don Quixote -- Don Quixote de la Mancha quix...@dulcineatech.com http://www.dulcineatech.com Dulcinea Technologies Corporation: Software of Elegance and Beauty. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Kernel boot problems or is my hard drive failing ?
2010/1/6 Linuxguy123 : > > Is anyone else experiencing a problem booting ? Does this sound like a > kernel problem or is my hard drive failing ? If your drive and BIOS supports S.M.A.R.T, then gnome-disk-utility (palimpsest) will tell you the status of your drive.. -c -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Kernel boot problems or is my hard drive failing ?
If I power down my laptop via the usual KStart->Shutdown means, it can take up to 4 restart attempts before it fully boots. It has no problem launching grub and the kernel selection screen. That it does reliably every time. After that, there are issues. Twice I will get a back screen with a flashing cursor. Then I will get an ehci -19 error. Then it will boot properly. My fscks are fine. I had a block error once, about two weeks ago, but that was with an older F12 kernel after completely crashing during a resume from suspend to RAM. Is anyone else experiencing a problem booting ? Does this sound like a kernel problem or is my hard drive failing ? Thanks $ uname -a Linux localhost.localdomain 2.6.31.9-174.fc12.i686.PAE #1 SMP Mon Dec 21 06:04:56 UTC 2009 i686 i686 i386 GNU/Linux -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: installing 64-bit kernel on a 32-bit system (nouveau issue?)
(warning: added cross posting to fedora-devel) Ramesh.R wrote: > > You can use 32 bit OS in 64 bit processor. > > 32 bit address bus will use 64 bit. MSB 32 bits will be idle.. > > But for the case, 64 bit OS in a 32 bit processor is not possible by theory. No one is talking about that. You are not the only one in this thread to have misunderstood. Suppose you have a 64 bit processor. You can run: (a) 64 bit kernel + 64 bit apps: that would be a pure 64 bit system (b) 64 bit kernel + 64 bit and 32 bit apps: that would be a multilib system, where you keep some 32 apps for some reasons A normal Fedora installation will give you case (a) or (b). Now, consider this: (c) 64 bit kernel + 32 bit apps: this is simply an extreme case of (b), a 64/32 system where every app is 32. Case (c) is interesting because: - you can switch a 32 bit install to this mode by simply installing a 64 bit kernel (and switch back at grub level any time you want) - the 64 bit kernel can handle all your memory better (faster) than 32 or 32+PAE kernel - you avoid the increased memory consumption of 64 bit apps (pointers are wider; there is big debate how much this impacts performance and if it is able to demolish the other improvements of x86_64 such as more regusters and SSE2 guaranteed avalability). Add to this that when you run 32 and 64 bit apps together you have both versions of the system libraries in memory, so the mem usage is higher. Finally, the discussion is: case (c) _SHOULD_ work perfectly in theory (see case (b)), but apparently there are a couple of bad spots for things no one ever run in 32 bit mode on 64 bit kernel. The first one I heard is the Nvidia closed source driver (ok, we already know closed source = unfixable problems), but this thread seems to suggest that nouveau has a similar issue. My suspicion is that it is just an untested area and a fix could be done easily. In any case, it looks like a show stopper for nvidia users. Best regards. -- Roberto Ragusamail at robertoragusa.it -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: installing 64-bit kernel on a 32-bit system
You can use 32 bit OS in 64 bit processor. 32 bit address bus will use 64 bit. MSB 32 bits will be idle.. But for the case, 64 bit OS in a 32 bit processor is not possible by theory. I did not think that it will work. Also i did not tried this. Any one tried this combination and working fine? Thanks. Best Regards, Ramesh Ramasamy. On Fri, Jan 1, 2010 at 11:10 AM, Roberto Ragusa wrote: > john wendel wrote: > > Just for fun, on F11 32-bit system (not tried on F12), I downloaded the > > latest F11 64-bit kernel package and installed it with > > > > rpm --nodeps --ignorearch --force > > > > It installed OK, since the kernel is pretty isolated from the rest of > > the system software. > > > > Booted into runlevel 3, and it worked fine. > > > > Now, X won't start because it needs the 64-bit nouveau driver. I don't > > know, but I suspect that you will need to install the entire 64-bit X > > server package(s). This will force you to install at least the 64-bit > > libc package. > > Interesting. > A similar problem had been described for the Nvidia closed driver; > same thing with noveau? not a good thing: the kernel-X interface > is expected to be cleaner in the open source driver... > > -- > Roberto Ragusamail at robertoragusa.it > > -- > fedora-list mailing list > fedora-list@redhat.com > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: > http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: installing 64-bit kernel on a 32-bit system
john wendel wrote: > Just for fun, on F11 32-bit system (not tried on F12), I downloaded the > latest F11 64-bit kernel package and installed it with > > rpm --nodeps --ignorearch --force > > It installed OK, since the kernel is pretty isolated from the rest of > the system software. > > Booted into runlevel 3, and it worked fine. > > Now, X won't start because it needs the 64-bit nouveau driver. I don't > know, but I suspect that you will need to install the entire 64-bit X > server package(s). This will force you to install at least the 64-bit > libc package. Interesting. A similar problem had been described for the Nvidia closed driver; same thing with noveau? not a good thing: the kernel-X interface is expected to be cleaner in the open source driver... -- Roberto Ragusamail at robertoragusa.it -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: installing 64-bit kernel on a 32-bit system
--- On Fri, 1/1/10, slamp slamp wrote: > Has anyone does this in Fedora 12? I > don't want to re-install the whole system. What did you do anyway? If you installed 64-bit F12 on a 32-bit system, it's not going to run even if you do install the 64-bit kernel. Everything is 64-bit, kernel, apps, utilities, etc. On a 32-bit system, everything has to be 32-bit. If that's the case, you're going to have to reinstall. Now, you can run the 32-bit distro on a 64-bit system, and on a 64-bit install on 64-bit hardware run 32-bit apps concurrently with 64-bit ones, but not the other way around. B -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: installing 64-bit kernel on a 32-bit system
*I think depends on your cpu type. What is your CPU? Intel Core 2 Duo** *--- Best Wishes, Waleed Harbi --- Try not to become a man of success but rather try to become a man of value. On Fri, Jan 1, 2010 at 5:24 PM, slamp slamp wrote: > Has anyone does this in Fedora 12? I don't want to re-install the whole > system. > > -- > fedora-list mailing list > fedora-list@redhat.com > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: > http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: installing 64-bit kernel on a 32-bit system
On 01/01/2010 06:24 AM, slamp slamp wrote: Has anyone does this in Fedora 12? I don't want to re-install the whole system. Just for fun, on F11 32-bit system (not tried on F12), I downloaded the latest F11 64-bit kernel package and installed it with rpm --nodeps --ignorearch --force It installed OK, since the kernel is pretty isolated from the rest of the system software. Booted into runlevel 3, and it worked fine. Now, X won't start because it needs the 64-bit nouveau driver. I don't know, but I suspect that you will need to install the entire 64-bit X server package(s). This will force you to install at least the 64-bit libc package. If you just want a 64-bit server without X, this would work fine. Otherwise I imagine you will get caught in package dependency hell and I'm too lazy this morning to follow it to the bitter end. Regards, John -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: installing 64-bit kernel on a 32-bit system
slamp slamp writes: > Has anyone does this in Fedora 12? I don't want to re-install the > whole system. I don't even think this is possible, and even if it is, my suspicion is you're asking for a lot of trouble. Just make a copy of your installed packages (rpm -qa), your home directories, then do a fresh install of F12, update, edit the package list to be a script of "yum installs" and run it, and copy your home directories back over. -- Randy Yates % "I met someone who looks alot like you, Digital Signal Labs % she does the things you do, mailto://ya...@ieee.org % but she is an IBM." http://www.digitalsignallabs.com %'Yours Truly, 2095', *Time*, ELO -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
installing 64-bit kernel on a 32-bit system
Has anyone does this in Fedora 12? I don't want to re-install the whole system. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Blocking auto-update of Kernel
On Wed, Dec 30, 2009 at 2:17 PM, Pikachu_2014 wrote: > > > 2009/12/30 James Allsopp > > Hi, >> Is there an option to stop the F12 auto-update system updating my >> kernel. I want to avoid a situation where my kernel gets updated but >> there isn't a matching Madwifi rpm in the repositories? >> >> Best regards >> James >> >> -- >> fedora-list mailing list >> fedora-list@redhat.com >> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list >> Guidelines: >> http://fedoraproject.org/wiki/Communicate/MailingListGuidelines >> > > Hi, > > by default yum keeps the last 3 kernels installed. But you can set yum to > keep all the updated kernels (see the installonly_limit key in > /etc/yum.conf). > > Anyway I don't know any third-party repository that still provides madwifi > drivers, since Atheros chipsets are supported by the vanilla kernel for a > moment. Why do you still need madwifi? Which repo providing madwifi for F12 > have you? > > Atheros drivers never worked reliably for me. I lost the connection with them every 5 min. I am still using ndiswrapper and the windows driver. I think it depends on the router one is using. -- Paulo Roma Cavalcanti LCG - UFRJ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Blocking auto-update of Kernel
On Wed, Dec 30, 2009 at 2:01 PM, James Allsopp wrote: > Hi, > Is there an option to stop the F12 auto-update system updating my > kernel. I want to avoid a situation where my kernel gets updated but > there isn't a matching Madwifi rpm in the repositories? > > Adding exclude=kernel* to you /etc/yum.conf? -- Paulo Roma Cavalcanti LCG - UFRJ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Blocking auto-update of Kernel
2009/12/30 James Allsopp > Hi, > Is there an option to stop the F12 auto-update system updating my > kernel. I want to avoid a situation where my kernel gets updated but > there isn't a matching Madwifi rpm in the repositories? > > Best regards > James > > -- > fedora-list mailing list > fedora-list@redhat.com > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: > http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > Hi, by default yum keeps the last 3 kernels installed. But you can set yum to keep all the updated kernels (see the installonly_limit key in /etc/yum.conf). Anyway I don't know any third-party repository that still provides madwifi drivers, since Atheros chipsets are supported by the vanilla kernel for a moment. Why do you still need madwifi? Which repo providing madwifi for F12 have you? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Blocking auto-update of Kernel
Hi, Is there an option to stop the F12 auto-update system updating my kernel. I want to avoid a situation where my kernel gets updated but there isn't a matching Madwifi rpm in the repositories? Best regards James -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: slow boot for latest fedora kernel 2.6.31.9-174.fc12.x86_64
On Wed, 2009-12-30 at 10:19 +1030, Tim wrote: > On Tue, 2009-12-29 at 20:00 +, N James Bridge wrote: > > Without "quiet" I still get no output at all for 2min 35sec, then > > normal rush of messages. Bootchart (very nice!) shows that the boot > > process itself is running normally, once it starts, about 45sec > > overall. The initial wait isn't shown on the chart. Once running, > > everything seems to be working. The entries in grub.conf are > > identical, except for version numbers. > > > > So what causes the wait? > > You haven't provided any details. *Exactly* what text appears before > the wait, and after the resumption? Before: nothing. Just the flashing underline character, in the same large typeface as the boot menu. After: flashing underline switches to a smaller size, then a message from plymouth (exactly the same for both versions of the kernel). plymouthd: ply_keyboard.c:450: ply_keyboard_add_input_handler: 'Assertion !=((void*)0)' failed. After this it continues as expected. -- N James Bridge -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Broadcom BCM4312 not working after updating the kernel [SOLVED]
My kernel is 32bit. I installed my fc12 with DVD iso. Mine didn't work until I update to 2.6.31.9-174.fc12.i686.PAE. Maybe, you should wait for the next kernel update. On Mon, Dec 28, 2009 at 7:20 PM, Jatin K wrote: > On 12/26/2009 11:28 PM, Jason Turning wrote: > >> Jatin K wrote: >> >> >>> My kernel is 64bit ( uname -a is as under ) >>> >>> uname -a >>> - >>> Linux jk-pc 2.6.31.9-174.fc12.x86_64 #1 SMP Mon Dec 21 05:33:33 UTC 2009 >>> x86_64 x86_64 x86_64 GNU/Linux >>> >>> >>> I've installed *kmod-wl-2.6.31.6-_166.fc12_.x86_64*as >>> kmod-wl-2.6.31.9-*_174.fc12_*.x86_64 is not available in repository .. >>> and I'm not able to install it using yum >>> >>> what can I do is there any source from where I can get >>> *_kmod-wl-2.6.31.9-174.fc12.x86_64_ * >>> >>> >> Just go back to using the previous kernel in your GRUB menu. You can edit >> your >> grub.conf file to select the previous kernel automatically. These issues >> usually work themselves out within a couple days with some new updates. >> After >> installing the new kernel I noticed the Nvidia driver wasn't working so I >> didn't get to the wifi, so I'm using the previous kernel until I notice a >> fresh >> batch of updates to try again. >> >> >> > > Today I got regular update from fedora or may be from rpmfusion . > installed it and my broadcom wireless BCM4312 working fine > > > yum log is as under > > > Dec 28 16:04:15 Updated: kmod-ndiswrapper-1.54-4.fc12.19.x86_64 > Dec 28 16:04:16 Updated: kmod-wl-5.10.91.9.3-3.fc12.11.x86_64 > > > > > -- > °v° > /(_)\ > ^ ^ Jatin Khatri > Registerd Linux user No #501175 > www.counter.li.org > No M$ > > -- > fedora-list mailing list > fedora-list@redhat.com > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: > http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > -- 自从一读楞严后，不看人间糟粕书。 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: slow boot for latest fedora kernel 2.6.31.9-174.fc12.x86_64
On Tue, 2009-12-29 at 20:00 +, N James Bridge wrote: > Without "quiet" I still get no output at all for 2min 35sec, then > normal rush of messages. Bootchart (very nice!) shows that the boot > process itself is running normally, once it starts, about 45sec > overall. The initial wait isn't shown on the chart. Once running, > everything seems to be working. The entries in grub.conf are > identical, except for version numbers. > > So what causes the wait? You haven't provided any details. *Exactly* what text appears before the wait, and after the resumption? -- [...@localhost ~]$ uname -r 2.6.27.25-78.2.56.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 Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: slow boot for latest fedora kernel 2.6.31.9-174.fc12.x86_64
On Tue, 2009-12-29 at 00:32 +, N James Bridge wrote: > Upgraded this evening and the system seemed broken but did start the > boot process after about 2 minutes. All normal thereafter. It doesn't > make any difference if I boot to level 3. After leaving the boot menu, > the screen simply displays a single underline character and nothing > happens at all for 2 min. Then things get underway at normal speed. > > Previous kernel is still installed and boots up quite normally. > > Any ideas? Anyone else getting the same behaviour? I use the nvidia > drivers but they are up to date and in any case shouldn't be used for a > level 3 boot. > -- > N James Bridge > Thanks for tips. Without "quiet" I still get no output at all for 2min 35sec, then normal rush of messages. Bootchart (very nice!) shows that the boot process itself is running normally, once it starts, about 45sec overall. The initial wait isn't shown on the chart. Once running, everything seems to be working. The entries in grub.conf are identical, except for version numbers. So what causes the wait? -- N James Bridge -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: slow boot for latest fedora kernel 2.6.31.9-174.fc12.x86_64
2009/12/29 Tom Horsley : > > I didn't have a problem, but you can see it spew a lot of info > about what is happening if you remove the "quiet" option > from the kernel boot line. That might give a clue where it > is spending time. Or run bootchart.. http://www.bootchart.org -c -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: slow boot for latest fedora kernel 2.6.31.9-174.fc12.x86_64
On Tue, 29 Dec 2009 00:32:07 + N James Bridge wrote: > Any ideas? Anyone else getting the same behaviour? I didn't have a problem, but you can see it spew a lot of info about what is happening if you remove the "quiet" option from the kernel boot line. That might give a clue where it is spending time. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
slow boot for latest fedora kernel 2.6.31.9-174.fc12.x86_64
Upgraded this evening and the system seemed broken but did start the boot process after about 2 minutes. All normal thereafter. It doesn't make any difference if I boot to level 3. After leaving the boot menu, the screen simply displays a single underline character and nothing happens at all for 2 min. Then things get underway at normal speed. Previous kernel is still installed and boots up quite normally. Any ideas? Anyone else getting the same behaviour? I use the nvidia drivers but they are up to date and in any case shouldn't be used for a level 3 boot. -- N James Bridge -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Broadcom BCM4312 not working after updating the kernel [SOLVED]
On 12/26/2009 11:28 PM, Jason Turning wrote: Jatin K wrote: My kernel is 64bit ( uname -a is as under ) uname -a - Linux jk-pc 2.6.31.9-174.fc12.x86_64 #1 SMP Mon Dec 21 05:33:33 UTC 2009 x86_64 x86_64 x86_64 GNU/Linux I've installed *kmod-wl-2.6.31.6-_166.fc12_.x86_64*as kmod-wl-2.6.31.9-*_174.fc12_*.x86_64 is not available in repository .. and I'm not able to install it using yum what can I do is there any source from where I can get *_kmod-wl-2.6.31.9-174.fc12.x86_64_ * Just go back to using the previous kernel in your GRUB menu. You can edit your grub.conf file to select the previous kernel automatically. These issues usually work themselves out within a couple days with some new updates. After installing the new kernel I noticed the Nvidia driver wasn't working so I didn't get to the wifi, so I'm using the previous kernel until I notice a fresh batch of updates to try again. Today I got regular update from fedora or may be from rpmfusion . installed it and my broadcom wireless BCM4312 working fine yum log is as under Dec 28 16:04:15 Updated: kmod-ndiswrapper-1.54-4.fc12.19.x86_64 Dec 28 16:04:16 Updated: kmod-wl-5.10.91.9.3-3.fc12.11.x86_64 -- °v° /(_)\ ^ ^ Jatin Khatri Registerd Linux user No #501175 www.counter.li.org No M$ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Broadcom BCM4312 not working after updating the kernel
Jatin K wrote: Dear all I've recently updated my kernel from *Linux 2.6.31.6-166.fc12.x86_64 *to *Linux 2.6.31.9-174.fc12.x86_64*, after that my wireless Brodcom BCM4312 is not working , on old kernel it was working fine ... if I boot into old kernel it works fine without any problem Does anyone faced this problem . how to solve this issue .. Help is appreciated Similar issue, prev. worked (2.6.31.5) this one doesn't. NIC starts up then shut back down. I had other issues, my synaptics touchpad stopped working as well. (https://bugzilla.redhat.com/show_bug.cgi?id=550719). I'm going to post a bug on that if I can catch it. Might be firmware, though... -- Bill Davidsen "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 Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Broadcom BCM4312 not working after updating the kernel
Jatin K wrote: > My kernel is 64bit ( uname -a is as under ) > > uname -a > - > Linux jk-pc 2.6.31.9-174.fc12.x86_64 #1 SMP Mon Dec 21 05:33:33 UTC 2009 > x86_64 x86_64 x86_64 GNU/Linux > > > I've installed *kmod-wl-2.6.31.6-_166.fc12_.x86_64*as > kmod-wl-2.6.31.9-*_174.fc12_*.x86_64 is not available in repository .. > and I'm not able to install it using yum > > what can I do is there any source from where I can get > *_kmod-wl-2.6.31.9-174.fc12.x86_64_ * Just go back to using the previous kernel in your GRUB menu. You can edit your grub.conf file to select the previous kernel automatically. These issues usually work themselves out within a couple days with some new updates. After installing the new kernel I noticed the Nvidia driver wasn't working so I didn't get to the wifi, so I'm using the previous kernel until I notice a fresh batch of updates to try again. -- Jason Turning -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Broadcom BCM4312 not working after updating the kernel
On 12/26/2009 01:47 PM, Athmane Madjoudj wrote: On Sat, Dec 26, 2009 at 8:14 AM, Jatin K wrote: On 12/26/2009 11:45 AM, Chris W Tucker wrote: Happened to me yesterday, I uninstalled drivers, then reinstalled through yum. It has worked since. Cheers, Chris On Sat, Dec 26, 2009 at 12:15 AM, Jatin Kmailto:ssh.fed...@gmail.com>> wrote: Dear all I've recently updated my kernel from *Linux 2.6.31.6-166.fc12.x86_64 *to *Linux 2.6.31.9-174.fc12.x86_64*, after that my wireless Brodcom BCM4312 is not working , on old kernel it was working fine ... if I boot into old kernel it works fine without any problem Does anyone faced this problem . how to solve this issue .. Help is appreciated Regards -- °v° /(_)\ ^ ^ Jatin Khatri Registerd Linux user No #501175 www.counter.li.org<http://www.counter.li.org> No M$ --fedora-list mailing list fedora-list@redhat.com<mailto:fedora-list@redhat.com> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines I've done it .but not working for me :-( Please tell me one thing which driver you are using for Brodcom BCM4312 form the following 1) broadcom-wl 5.10.91.9.3-1fc12 (noarch) 2) ndiswrapper 1.54-2.fc11 or 3) Broadcom provided driver 802.11 Linux STA driver ( downloaded from http://www.broadcom.com/support/802.11/linux_sta.php ) Regards -- °v° /(_)\ ^ ^ Jatin Khatri Registerd Linux user No #501175 www.counter.li.org No M$ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines In my case i have a Broadcom BCM4312 (HP Notebook), it works with the following packages (don't forget to power-on the wifi): kmod-wl-2.6.31.9-174.fc12.i686-5.10.91.9.3-3.fc12.6.i686 kmod-wl-5.10.91.9.3-3.fc12.10.i686 broadcom-wl-5.10.91.9.3-1.fc12.noarch My kernel is 64bit ( uname -a is as under ) uname -a - Linux jk-pc 2.6.31.9-174.fc12.x86_64 #1 SMP Mon Dec 21 05:33:33 UTC 2009 x86_64 x86_64 x86_64 GNU/Linux I've installed *kmod-wl-2.6.31.6-_166.fc12_.x86_64*as kmod-wl-2.6.31.9-*_174.fc12_*.x86_64 is not available in repository .. and I'm not able to install it using yum what can I do is there any source from where I can get *_kmod-wl-2.6.31.9-174.fc12.x86_64_ * Regards -- °v° /(_)\ ^ ^ Jatin Khatri Registerd Linux user No #501175 www.counter.li.org No M$ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Broadcom BCM4312 not working after updating the kernel
On Sat, Dec 26, 2009 at 8:14 AM, Jatin K wrote: > On 12/26/2009 11:45 AM, Chris W Tucker wrote: >> >> Happened to me yesterday, >> I uninstalled drivers, then reinstalled through yum. >> It has worked since. >> Cheers, >> Chris >> >> >> On Sat, Dec 26, 2009 at 12:15 AM, Jatin K > <mailto:ssh.fed...@gmail.com>> wrote: >> >> Dear all >> >> I've recently updated my kernel from *Linux >> 2.6.31.6-166.fc12.x86_64 *to *Linux 2.6.31.9-174.fc12.x86_64*, >> after that my wireless Brodcom BCM4312 is not working , on old >> kernel it was working fine ... if I boot into old kernel it works >> fine without any problem >> >> Does anyone faced this problem . how to solve this issue .. >> Help is appreciated >> >> >> Regards >> >> -- °v° >> /(_)\ >> ^ ^ Jatin Khatri >> Registerd Linux user No #501175 >> www.counter.li.org <http://www.counter.li.org> >> No M$ >> >> -- fedora-list mailing list >> fedora-l...@redhat.com <mailto:fedora-list@redhat.com> >> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list >> Guidelines: >> http://fedoraproject.org/wiki/Communicate/MailingListGuidelines >> >> > I've done it .but not working for me :-( > > Please tell me one thing which driver you are using for Brodcom BCM4312 > form the following > > 1) broadcom-wl 5.10.91.9.3-1fc12 (noarch) > > 2) ndiswrapper 1.54-2.fc11 > > or > > 3) Broadcom provided driver 802.11 Linux STA driver ( downloaded from > http://www.broadcom.com/support/802.11/linux_sta.php ) > > > > Regards > -- > > °v° > /(_)\ > ^ ^ Jatin Khatri > Registerd Linux user No #501175 > www.counter.li.org > No M$ > > -- > fedora-list mailing list > fedora-list@redhat.com > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > In my case i have a Broadcom BCM4312 (HP Notebook), it works with the following packages (don't forget to power-on the wifi): kmod-wl-2.6.31.9-174.fc12.i686-5.10.91.9.3-3.fc12.6.i686 kmod-wl-5.10.91.9.3-3.fc12.10.i686 broadcom-wl-5.10.91.9.3-1.fc12.noarch -- Athmane Madjoudj -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Broadcom BCM4312 not working after updating the kernel
On 12/26/2009 11:45 AM, Chris W Tucker wrote: Happened to me yesterday, I uninstalled drivers, then reinstalled through yum. It has worked since. Cheers, Chris On Sat, Dec 26, 2009 at 12:15 AM, Jatin K <mailto:ssh.fed...@gmail.com>> wrote: Dear all I've recently updated my kernel from *Linux 2.6.31.6-166.fc12.x86_64 *to *Linux 2.6.31.9-174.fc12.x86_64*, after that my wireless Brodcom BCM4312 is not working , on old kernel it was working fine ... if I boot into old kernel it works fine without any problem Does anyone faced this problem . how to solve this issue .. Help is appreciated Regards -- °v° /(_)\ ^ ^ Jatin Khatri Registerd Linux user No #501175 www.counter.li.org <http://www.counter.li.org> No M$ -- fedora-list mailing list fedora-list@redhat.com <mailto:fedora-list@redhat.com> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines I've done it .but not working for me :-( Please tell me one thing which driver you are using for Brodcom BCM4312 form the following 1) broadcom-wl 5.10.91.9.3-1fc12 (noarch) 2) ndiswrapper 1.54-2.fc11 or 3) Broadcom provided driver 802.11 Linux STA driver ( downloaded from http://www.broadcom.com/support/802.11/linux_sta.php ) Regards -- °v° /(_)\ ^ ^ Jatin Khatri Registerd Linux user No #501175 www.counter.li.org No M$ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Broadcom BCM4312 not working after updating the kernel
Happened to me yesterday, I uninstalled drivers, then reinstalled through yum. It has worked since. Cheers, Chris On Sat, Dec 26, 2009 at 12:15 AM, Jatin K wrote: > Dear all > > I've recently updated my kernel from *Linux 2.6.31.6-166.fc12.x86_64 *to > *Linux 2.6.31.9-174.fc12.x86_64*, after that my wireless Brodcom BCM4312 is > not working , on old kernel it was working fine ... if I boot into old > kernel it works fine without any problem > > Does anyone faced this problem . how to solve this issue .. Help is > appreciated > > > Regards > > -- > °v° > /(_)\ > ^ ^ Jatin Khatri > Registerd Linux user No #501175 > www.counter.li.org > No M$ > > -- > fedora-list mailing list > fedora-list@redhat.com > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: > http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Broadcom BCM4312 not working after updating the kernel
Dear all I've recently updated my kernel from *Linux 2.6.31.6-166.fc12.x86_64 *to *Linux 2.6.31.9-174.fc12.x86_64*, after that my wireless Brodcom BCM4312 is not working , on old kernel it was working fine ... if I boot into old kernel it works fine without any problem Does anyone faced this problem . how to solve this issue .. Help is appreciated Regards -- °v° /(_)\ ^ ^ Jatin Khatri Registerd Linux user No #501175 www.counter.li.org No M$ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Daily Kernel Panics
On 12/20/2009 10:44 AM, Hiisi wrote: > 2009/12/20 Steven Stern : >> On 12/19/2009 10:29 PM, Bill Davidsen wrote: >>> Steven Stern wrote: >>>> On 12/13/2009 07:25 AM, Globe Trotter wrote: >>> > <--SNIP--> >>>> >>> Note that in the above example of a stable system, item 3. I have had >>> about equal numbers of people tell me that the vendor driver is vastly >>> more stable than the built-in driver, and totally the opposite. >>> >>> Oh, and some fundamentalist open source fanatics who tell me it's better >>> to crash a few times a day than use a closed source driver. ;-) >>> >>> The only "desktop effect" of interest to me is stability. >>> >> >> Agreed on your final point. Just for grins, I'm downloading and will >> try the Radeon X300 drivers directly from ATI with Compiz enabled. >> >> >> >> -- >> >> Steve > > 'Directly from ATI' you will have to compile them manually. I think > it's better use rpm [1]. > Just my 2 cents... > > Links: > 1. http://rpmfusion.org/RPMFusionSwitcher I found that out. The ATI drivers don't like the current kernel. I'm using rpmfusion (for the codecs), but I don't see any ATI drivers there. -- Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Daily Kernel Panics
2009/12/20 Steven Stern : > On 12/19/2009 10:29 PM, Bill Davidsen wrote: >> Steven Stern wrote: >>> On 12/13/2009 07:25 AM, Globe Trotter wrote: >> <--SNIP--> >>> >> Note that in the above example of a stable system, item 3. I have had >> about equal numbers of people tell me that the vendor driver is vastly >> more stable than the built-in driver, and totally the opposite. >> >> Oh, and some fundamentalist open source fanatics who tell me it's better >> to crash a few times a day than use a closed source driver. ;-) >> >> The only "desktop effect" of interest to me is stability. >> > > Agreed on your final point. Just for grins, I'm downloading and will > try the Radeon X300 drivers directly from ATI with Compiz enabled. > > > > -- > > Steve 'Directly from ATI' you will have to compile them manually. I think it's better use rpm [1]. Just my 2 cents... Links: 1. http://rpmfusion.org/RPMFusionSwitcher -- Hiisi. Registered Linux User #487982. Be counted at: http://counter.li.org/ -- Spandex is a privilege, not a right. -- SIP: hi...@ekiga.net -- pub 1024D/085B139A -- Powered by Fedora: http://fedoraproject.org/ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Daily Kernel Panics
On 12/19/2009 10:29 PM, Bill Davidsen wrote: > Steven Stern wrote: >> On 12/13/2009 07:25 AM, Globe Trotter wrote: > Do you have desktop effects enabled? I found that my system is much more stable with desktop effects turned off [1]. My video is ATI [2] with driver 'ati' [3]. Footmarks: 1. ~]$ uptime 10:27:28 up 3 days, 9:22, 3 users, load average: 0.25, 0.22, 0.18 2. ~]$ lspci [--SNIP--] 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600] 01:00.1 Display controller: ATI Technologies Inc RV350 AP [Radeon 9600] (Secondary) 3. ati - Vendor-supplied driver for ati cards >> >> >> I do have an ATI card. I'll try turning off desktop effects. Removing >> glx-utils removes all of compiz! >> >> 01:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 >> [Radeon X300 (PCIE)] >> 01:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE] >> > Note that in the above example of a stable system, item 3. I have had > about equal numbers of people tell me that the vendor driver is vastly > more stable than the built-in driver, and totally the opposite. > > Oh, and some fundamentalist open source fanatics who tell me it's better > to crash a few times a day than use a closed source driver. ;-) > > The only "desktop effect" of interest to me is stability. > Agreed on your final point. Just for grins, I'm downloading and will try the Radeon X300 drivers directly from ATI with Compiz enabled. -- Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: How to compile a kernel?
Am Sonntag, den 20.12.2009, 10:35 + schrieb 严晶涛: > I'm sorry with my bad English. No problem. ;) > I'm using Fedora 12 X86_64 > I have downloaded a kernel(2.6.32.2). > Then,I do these: > cd linux-2.6.32.2 > cp /boot/config-`uname -r` .config > make menuconfig > make all > make modules_install > make install > reboot > > When I choose the new kernel,I found it's very slow when run with X,I > spend 5 minutes to open gnome,and It's too hard to run any > application. > > How to solve this? Please follow the instructions from http://fedoraproject.org/wiki/Building_a_custom_kernel Regards, Christoph -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
How to compile a kernel?
I'm sorry with my bad English. I'm using Fedora 12 X86_64 I have downloaded a kernel(2.6.32.2). Then,I do these: cd linux-2.6.32.2 cp /boot/config-`uname -r` .config make menuconfig make all make modules_install make install reboot When I choose the new kernel,I found it's very slow when run with X,I spend 5 minutes to open gnome,and It's too hard to run any application. How to solve this? _ 上Windows Live 中国首页，下载Messenger2009安全版！ http://www.windowslive.cn-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Daily Kernel Panics
Steven Stern wrote: On 12/13/2009 07:25 AM, Globe Trotter wrote: Do you have desktop effects enabled? I found that my system is much more stable with desktop effects turned off [1]. My video is ATI [2] with driver 'ati' [3]. Footmarks: 1. ~]$ uptime 10:27:28 up 3 days, 9:22, 3 users, load average: 0.25, 0.22, 0.18 2. ~]$ lspci [--SNIP--] 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600] 01:00.1 Display controller: ATI Technologies Inc RV350 AP [Radeon 9600] (Secondary) 3. ati - Vendor-supplied driver for ati cards I do have an ATI card. I'll try turning off desktop effects. Removing glx-utils removes all of compiz! 01:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] 01:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE] Note that in the above example of a stable system, item 3. I have had about equal numbers of people tell me that the vendor driver is vastly more stable than the built-in driver, and totally the opposite. Oh, and some fundamentalist open source fanatics who tell me it's better to crash a few times a day than use a closed source driver. ;-) The only "desktop effect" of interest to me is stability. -- Bill Davidsen "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 Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Daily Kernel Panics
2009/12/18 Steven Stern > > On 12/13/2009 10:32 AM, Steven Stern wrote: <--SNIP--> >>> >>> I have had this problem in the past with Fedora 9, I believe using ATI >>> graphics cards. I tracked it down to glxgears (posted to this group >>> then) getting invoked and eliminated it to get around this problem. >>> Specifically, I did >>> >>> yum erase glx-utils >>> >>> This may not work for you because you may use glxgears for something >>> but it did work for me. >>> >>> Best wishes, >>> T <--SNIP--> > > Steve > Do you have desktop effects enabled? I found that my system is much more stable with desktop effects turned off [1]. My video <--SNIP--> >> > > Just for the record. Since I've turned off desktop effects, the frequent > crashes are gone. > > -- > > Steve > Since I've yumerased glx-utils the problem has gone at all. Now my system is stable like a Linux ;-) -- Hiisi. Registered Linux User #487982. Be counted at: http://counter.li.org/ -- Spandex is a privilege, not a right. -- SIP: hi...@ekiga.net -- pub 1024D/085B139A -- Powered by Fedora: http://fedoraproject.org/ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Daily Kernel Panics
On 12/13/2009 10:32 AM, Steven Stern wrote: On 12/13/2009 07:25 AM, Globe Trotter wrote: --- On Sun, 12/13/09, Hiisi wrote: From: Hiisi Subject: Re: Daily Kernel Panics To: "Community assistance, encouragement, and advice for using Fedora." Date: Sunday, December 13, 2009, 2:34 AM 2009/12/12 Steven Stern: On 12/11/2009 03:45 PM, Hiisi wrote: 2009/12/11 Steven Stern: How do I report these? I get about one a day, typically while in Firefox and doing something else. The machine locks up tight (flashing num and scroll locks) and requires power cycling and nothing seems to get logged. Abrt doesn't see it after restart. I have had this problem in the past with Fedora 9, I believe using ATI graphics cards. I tracked it down to glxgears (posted to this group then) getting invoked and eliminated it to get around this problem. Specifically, I did yum erase glx-utils This may not work for you because you may use glxgears for something but it did work for me. Best wishes, T -- Steve The same here: Linux ***.** 2.6.30.9-102.fc11.i586 #1 SMP Thu Dec 3 23:46:37 EST 2009 i686 i686 i386 GNU/Linux And yes, Firefox is not always involved. I've already asked the question on this list (haven't received any responses). How do you know it's kernel panic? When the machine locks up, the caps-lock and scroll-light both flash. What's really annoying is that if I'm playing music, it gets really weird and scares the cats. -- Steve Do you have desktop effects enabled? I found that my system is much more stable with desktop effects turned off [1]. My video is ATI [2] with driver 'ati' [3]. Footmarks: 1. ~]$ uptime 10:27:28 up 3 days, 9:22, 3 users, load average: 0.25, 0.22, 0.18 2. ~]$ lspci [--SNIP--] 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600] 01:00.1 Display controller: ATI Technologies Inc RV350 AP [Radeon 9600] (Secondary) 3. ati - Vendor-supplied driver for ati cards I do have an ATI card. I'll try turning off desktop effects. Removing glx-utils removes all of compiz! 01:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] 01:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE] Just for the record. Since I've turned off desktop effects, the frequent crashes are gone. -- Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: no kernel in updates-testing?
On 15/12/09 17:56, Konstantin Svist wrote: > On 12/15/2009 09:44 AM, Frank Murphy (Frankly3D) wrote: >> On 15/12/09 17:42, Konstantin Svist wrote: >> >>> How come I don't see fresh kernel versions in updates-testing? Should I >>> be looking elsewhere? >>> >>> >> The infrastructure just moved house. >> Give them a chance. >> >> > > Sorry, I must've missed that. What's the new infrastructure? > https://fedorahosted.org/fedora-infrastructure/ticket/1845 -- Regards, Frank Murphy UTF_8 Encoded. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: no kernel in updates-testing?
On 12/15/2009 09:44 AM, Frank Murphy (Frankly3D) wrote: On 15/12/09 17:42, Konstantin Svist wrote: How come I don't see fresh kernel versions in updates-testing? Should I be looking elsewhere? The infrastructure just moved house. Give them a chance. Sorry, I must've missed that. What's the new infrastructure? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: no kernel in updates-testing?
On 15/12/09 17:42, Konstantin Svist wrote: > How come I don't see fresh kernel versions in updates-testing? Should I > be looking elsewhere? > The infrastructure just moved house. Give them a chance. -- Regards, Frank Murphy UTF_8 Encoded. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
no kernel in updates-testing?
How come I don't see fresh kernel versions in updates-testing? Should I be looking elsewhere? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Errormessage - Dec 13 19:48:25 localhost kernel: hub 1-4:1.0: over-current change on port 2
On Mon, Dec 14, 2009 at 7:35 AM, Mikkel wrote: > On 12/13/2009 08:53 PM, Paolo Galtieri wrote: > > I'm getting lots of these messages in /var/log/messages > > > > Dec 13 19:48:25 localhost kernel: hub 1-4:1.0: over-current change on > port 2 > > > > They're coming out about one per second. Anybody know what to do about > it? > > > > port 2 is my Logitech web cam. They keep coming even after I stop the > > camera. > > > > It stops once I disconnect the hub. > > > > > > Paolo > > > Dumb question 1 - is it a self powered or bus powered hub? (Does it > have its own power supply?) > It has its own power supply > Dumb question 2 - do you get the messages if you plug the web cam in > direct instead of using the hub? > The message does not show up if I plug the camera directly into the system. However, do I get the following message: Dec 14 08:46:42 localhost pulseaudio[2050]: alsa-mixer.c: Your kernel driver is broken: it reports a volume range from 18.00 dB to 18.00 dB which makes no sense. I still get the message if I plug the hub back in, even though there is nothing in port 2. Paolo > Mikkel > -- > > Do not meddle in the affairs of dragons, > for thou art crunchy and taste good with Ketchup! > > > -- > fedora-list mailing list > fedora-list@redhat.com > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: > http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Errormessage - Dec 13 19:48:25 localhost kernel: hub 1-4:1.0: over-current change on port 2
On 12/13/2009 08:53 PM, Paolo Galtieri wrote: > I'm getting lots of these messages in /var/log/messages > > Dec 13 19:48:25 localhost kernel: hub 1-4:1.0: over-current change on port 2 > > They're coming out about one per second. Anybody know what to do about it? > > port 2 is my Logitech web cam. They keep coming even after I stop the > camera. > > It stops once I disconnect the hub. > > > Paolo > Dumb question 1 - is it a self powered or bus powered hub? (Does it have its own power supply?) Dumb question 2 - do you get the messages if you plug the web cam in direct instead of using the hub? 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 Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: kernel error message from pulseaudio
2009/12/14 Paolo Galtieri : > I see lots of the following message > > Dec 13 23:56:17 localhost pulseaudio[2050]: alsa-mixer.c: Your kernel driver > is broken: it reports a volume range from 18.00 dB to 18.00 dB which makes > no sense. etc. > Can anyone tell me what the cause of this is and how ti fix it? As it suggests your kernel driver is reporting incorrect information to the mixer. It will need to be fixed, the best thing you can do is file a bug against the kernel in Fedora bugzilla and attach the file generated by running: alsa-info.sh --no-upload And including this dmesg error and a description of any other sound related problems you have that might be relevant. -- imalone -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
kernel error message from pulseaudio
I see lots of the following message Dec 13 23:56:17 localhost pulseaudio[2050]: alsa-mixer.c: Your kernel driver is broken: it reports a volume range from 18.00 dB to 18.00 dB which makes no sense. Dec 13 23:56:17 localhost pulseaudio[2050]: alsa-mixer.c: Your kernel driver is broken: it reports a volume range from 18.00 dB to 18.00 dB which makes no sense. Dec 13 23:56:17 localhost pulseaudio[2050]: alsa-mixer.c: Your kernel driver is broken: it reports a volume range from 18.00 dB to 18.00 dB which makes no sense. Dec 13 23:56:17 localhost pulseaudio[2050]: alsa-mixer.c: Your kernel driver is broken: it reports a volume range from 18.00 dB to 18.00 dB which makes no sense. Dec 13 23:56:17 localhost pulseaudio[2050]: alsa-mixer.c: Your kernel driver is broken: it reports a volume range from 18.00 dB to 18.00 dB which makes no sense. Dec 13 23:56:17 localhost pulseaudio[2050]: alsa-mixer.c: Your kernel driver is broken: it reports a volume range from 18.00 dB to 18.00 dB which makes no sense Can anyone tell me what the cause of this is and how ti fix it? Paolo -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Errormessage - Dec 13 19:48:25 localhost kernel: hub 1-4:1.0: over-current change on port 2
I'm getting lots of these messages in /var/log/messages Dec 13 19:48:25 localhost kernel: hub 1-4:1.0: over-current change on port 2 They're coming out about one per second. Anybody know what to do about it? port 2 is my Logitech web cam. They keep coming even after I stop the camera. It stops once I disconnect the hub. Paolo -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Daily Kernel Panics
2009/12/13 Steven Stern : > On 12/13/2009 07:25 AM, Globe Trotter wrote: >> >> --- On Sun, 12/13/09, Hiisi wrote: >> <--SNIP--> >> >> I have had this problem in the past with Fedora 9, I believe using ATI >> graphics cards. I tracked it down to glxgears (posted to this group then) >> getting invoked and eliminated it to get around this problem. Specifically, >> I did >> >> yum erase glx-utils >> >> This may not work for you because you may use glxgears for something but >> it did work for me. >> >> Best wishes, >> T >> <--SNIP--> > > I do have an ATI card. I'll try turning off desktop effects. Removing > glx-utils removes all of compiz! > Yes! And I can live without it and without emerald themes. So, I did 'yum erase glx-utils'... > -- > > Steve > -- Hiisi. Registered Linux User #487982. Be counted at: http://counter.li.org/ -- Spandex is a privilege, not a right. -- SIP: hi...@ekiga.net -- pub 1024D/085B139A -- Powered by Fedora: http://fedoraproject.org/ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Daily Kernel Panics
On 12/13/2009 07:25 AM, Globe Trotter wrote: --- On Sun, 12/13/09, Hiisi wrote: From: Hiisi Subject: Re: Daily Kernel Panics To: "Community assistance, encouragement, and advice for using Fedora." Date: Sunday, December 13, 2009, 2:34 AM 2009/12/12 Steven Stern: On 12/11/2009 03:45 PM, Hiisi wrote: 2009/12/11 Steven Stern: How do I report these? I get about one a day, typically while in Firefox and doing something else. The machine locks up tight (flashing num and scroll locks) and requires power cycling and nothing seems to get logged. Abrt doesn't see it after restart. I have had this problem in the past with Fedora 9, I believe using ATI graphics cards. I tracked it down to glxgears (posted to this group then) getting invoked and eliminated it to get around this problem. Specifically, I did yum erase glx-utils This may not work for you because you may use glxgears for something but it did work for me. Best wishes, T -- Steve The same here: Linux ***.** 2.6.30.9-102.fc11.i586 #1 SMP Thu Dec 3 23:46:37 EST 2009 i686 i686 i386 GNU/Linux And yes, Firefox is not always involved. I've already asked the question on this list (haven't received any responses). How do you know it's kernel panic? When the machine locks up, the caps-lock and scroll-light both flash. What's really annoying is that if I'm playing music, it gets really weird and scares the cats. -- Steve Do you have desktop effects enabled? I found that my system is much more stable with desktop effects turned off [1]. My video is ATI [2] with driver 'ati' [3]. Footmarks: 1. ~]$ uptime 10:27:28 up 3 days, 9:22, 3 users, load average: 0.25, 0.22, 0.18 2. ~]$ lspci [--SNIP--] 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600] 01:00.1 Display controller: ATI Technologies Inc RV350 AP [Radeon 9600] (Secondary) 3. ati - Vendor-supplied driver for ati cards I do have an ATI card. I'll try turning off desktop effects. Removing glx-utils removes all of compiz! 01:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] 01:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE] -- Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: f12 updates kernel nomodeset option breaks radeon
Hi John, My F12 worked perfectly on my ATI Technologies Inc RV350 AS [Radeon 9550] with no xorg.conf from the first day. After couple of updates compiz started crashing and xrandr stopped recognizing settings properly. I used xorg.conf for a while only as a work around. Now after couple of recent udpates, I found that it works fine again with no xorg.conf except I need to xrandr -s 0 to restore settings for my display and I had to edit settings for compiz to make it work properly again. -- -- Grzegorz Witkowski :: gesli...@gmail.com :Gadu-Gadu: 5942122 :ICQ: 427096157 :Skype: gesirl -- 01000111 01100101 01110011 01100011 0111 0111 01100101 http://counter.li.org #239224 Registration 2001-10-29 07:19:32 -= GNU/Linux - The Experience of Freedom =- -Original Message- From: Skunk Worx Reply-to: "Community assistance, encouragement, and advice for using Fedora." To: For users of Fedora Core releases Subject: f12 updates kernel nomodeset option breaks radeon Date: Sun, 29 Nov 2009 16:27:59 -0800 After updates today my radeon driver does not start properly if the kernel nomodeset option is used. The X log has a message : "Couldn't find valid PLL dividers" Good news though in other areas : --I can shell into the machine with ssh, it's not a hard crash. --If I set up the kernel with "rhgb quiet" and do not use the "nomodeset" option X starts up normally. --I no longer need an xorg.conf with "XAA" accel enabled to prevent X crashes. EXA seems to be working reliably now. (I previously reported that www.newegg.com and wiki.centos.org were crashing X with EXA enabled.) EXA seems stable with kernel modesetting though...great! Smolt : http://www.smolts.org/client/show/pub_2eb94c68-e819-4003-aa96-47783092c4ab --- John -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Daily Kernel Panics
--- On Sun, 12/13/09, Hiisi wrote: > From: Hiisi > Subject: Re: Daily Kernel Panics > To: "Community assistance, encouragement, and advice for using Fedora." > > Date: Sunday, December 13, 2009, 2:34 AM > 2009/12/12 Steven Stern : > > On 12/11/2009 03:45 PM, Hiisi wrote: > >> > >> 2009/12/11 Steven Stern: > >>> > >>> How do I report these? I get about one a day, > typically while in Firefox > >>> and > >>> doing something else. The machine locks up > tight (flashing num and > >>> scroll > >>> locks) and requires power cycling and nothing > seems to get logged. Abrt > >>> doesn't see it after restart. > >>> > >>> I have had this problem in the past with Fedora 9, I believe using ATI graphics cards. I tracked it down to glxgears (posted to this group then) getting invoked and eliminated it to get around this problem. Specifically, I did yum erase glx-utils This may not work for you because you may use glxgears for something but it did work for me. Best wishes, T > >>> -- > >>> > >>> Steve > >>> > >> > >> The same here: > >> Linux ***.** 2.6.30.9-102.fc11.i586 #1 SMP Thu Dec > 3 23:46:37 EST 2009 > >> i686 i686 i386 GNU/Linux > >> And yes, Firefox is not always involved. I've > already asked the > >> question on this list (haven't received any > responses). > >> How do you know it's kernel panic? > > > > When the machine locks up, the caps-lock and > scroll-light both flash. What's > > really annoying is that if I'm playing music, it gets > really weird and > > scares the cats. > > > > -- > > > > Steve > > > > Do you have desktop effects enabled? I found that my system > is much > more stable with desktop effects turned off [1]. My video > is ATI [2] > with driver 'ati' [3]. > > Footmarks: > 1. ~]$ uptime > 10:27:28 up 3 days, 9:22, 3 users, load > average: 0.25, 0.22, 0.18 > 2. ~]$ lspci > [--SNIP--] > 01:00.0 VGA compatible controller: ATI Technologies Inc > RV350 AP [Radeon 9600] > 01:00.1 Display controller: ATI Technologies Inc RV350 AP > [Radeon > 9600] (Secondary) > 3. ati - Vendor-supplied driver for ati cards > -- > Hiisi. > Registered Linux User #487982. Be counted at: http://counter.li.org/ > -- > Spandex is a privilege, not a right. > -- > SIP: hi...@ekiga.net > -- > pub 1024D/085B139A > -- > Powered by Fedora: > http://fedoraproject.org/ > > -- > fedora-list mailing list > fedora-list@redhat.com > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Daily Kernel Panics
2009/12/12 Steven Stern : > On 12/11/2009 03:45 PM, Hiisi wrote: >> >> 2009/12/11 Steven Stern: >>> >>> How do I report these? I get about one a day, typically while in Firefox >>> and >>> doing something else. The machine locks up tight (flashing num and >>> scroll >>> locks) and requires power cycling and nothing seems to get logged. Abrt >>> doesn't see it after restart. >>> >>> >>> -- >>> >>> Steve >>> >> >> The same here: >> Linux ***.** 2.6.30.9-102.fc11.i586 #1 SMP Thu Dec 3 23:46:37 EST 2009 >> i686 i686 i386 GNU/Linux >> And yes, Firefox is not always involved. I've already asked the >> question on this list (haven't received any responses). >> How do you know it's kernel panic? > > When the machine locks up, the caps-lock and scroll-light both flash. What's > really annoying is that if I'm playing music, it gets really weird and > scares the cats. > > -- > > Steve > Do you have desktop effects enabled? I found that my system is much more stable with desktop effects turned off [1]. My video is ATI [2] with driver 'ati' [3]. Footmarks: 1. ~]$ uptime 10:27:28 up 3 days, 9:22, 3 users, load average: 0.25, 0.22, 0.18 2. ~]$ lspci [--SNIP--] 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600] 01:00.1 Display controller: ATI Technologies Inc RV350 AP [Radeon 9600] (Secondary) 3. ati - Vendor-supplied driver for ati cards -- Hiisi. Registered Linux User #487982. Be counted at: http://counter.li.org/ -- Spandex is a privilege, not a right. -- SIP: hi...@ekiga.net -- pub 1024D/085B139A -- Powered by Fedora: http://fedoraproject.org/ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
After Fedora 12 kernel updates, grub doesn't remember previous settings
After each new kernel update in Fedora 12 x86_64 , default time out is reset to 15secs and freshly installed kernel is set as default. Since the proprietary WLAN drivers from RPMFusion comes one or two days after each kernel update, after each kernel update I have to manually edit settings for grub bootloader. In Fedora 11 I did not have this issue. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Daily Kernel Panics
On 12/11/2009 03:45 PM, Hiisi wrote: 2009/12/11 Steven Stern: How do I report these? I get about one a day, typically while in Firefox and doing something else. The machine locks up tight (flashing num and scroll locks) and requires power cycling and nothing seems to get logged. Abrt doesn't see it after restart. -- Steve The same here: Linux ***.** 2.6.30.9-102.fc11.i586 #1 SMP Thu Dec 3 23:46:37 EST 2009 i686 i686 i386 GNU/Linux And yes, Firefox is not always involved. I've already asked the question on this list (haven't received any responses). How do you know it's kernel panic? When the machine locks up, the caps-lock and scroll-light both flash. What's really annoying is that if I'm playing music, it gets really weird and scares the cats. -- Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Daily Kernel Panics
2009/12/11 Steven Stern : > How do I report these? I get about one a day, typically while in Firefox and > doing something else. The machine locks up tight (flashing num and scroll > locks) and requires power cycling and nothing seems to get logged. Abrt > doesn't see it after restart. > > > -- > > Steve > The same here: Linux ***.** 2.6.30.9-102.fc11.i586 #1 SMP Thu Dec 3 23:46:37 EST 2009 i686 i686 i386 GNU/Linux And yes, Firefox is not always involved. I've already asked the question on this list (haven't received any responses). How do you know it's kernel panic? -- Hiisi. Registered Linux User #487982. Be counted at: http://counter.li.org/ -- Spandex is a privilege, not a right. -- SIP: hi...@ekiga.net -- pub 1024D/085B139A -- Powered by Fedora: http://fedoraproject.org/ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Daily Kernel Panics
On 12/11/2009 12:51 PM, Frank Cox wrote: On Fri, 2009-12-11 at 12:11 -0600, Steven Stern wrote: I get about one a day, typically while in Firefox and doing something else. The machine locks up tight (flashing num and scroll locks) and requires power cycling and nothing seems to get logged. Remove your firefox plugins and extensions and see if the problem goes away. Firefox is not always involved. Thus, my question on how I find a log or some real data and report it. -- Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Daily Kernel Panics
On Fri, 2009-12-11 at 12:11 -0600, Steven Stern wrote: > I get about one a day, typically while in Firefox > and doing something else. The machine locks up tight (flashing num > and > scroll locks) and requires power cycling and nothing seems to get > logged. Remove your firefox plugins and extensions and see if the problem goes away. -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Daily Kernel Panics
How do I report these? I get about one a day, typically while in Firefox and doing something else. The machine locks up tight (flashing num and scroll locks) and requires power cycling and nothing seems to get logged. Abrt doesn't see it after restart. -- Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F12 Wireless disabled with kernel 2.6.31.6-162
Richard England wrote: pro/wireless 2200BG in a Dell Latitude D410. F12 Fully updated (as of 7 December). With Kernel 2.6.31.6-162.fc12.i686 the wireless is completely disabled. This was the latest kernel installed. Backing down to kernel 2.6.31.6-145.fc12.i686 everything returns to normal. This was the immediately preceding kernel I had. Any one confirm this? I looked for a BZ entry but I'm notoriously bad at finding things there Did you have a 3rd party driver installed, like kmod-wl or similar? If so did you update that? Boot your old kernel and see what driver is in use. If it's not a Fedora driver you are on your own. At least people here are polite, LKML is less so on occasion. ;-) -- Bill Davidsen "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 Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Latest Kernel causes reboot hell
On Wed, 09 Dec 2009 07:13:30 -0500 Sam Varshavchik wrote: > I think there's a way to install a one-time only grub configuration file, > for the next boot. There are two ways: The one documented in the grub info file, and the one that actually works :-). Both involve "savedefault", but the grub "help savedefault" info is correct and the info file description of savedefault is completely bogus. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Latest Kernel causes reboot hell
Ian Malone writes: Yes, it does look more polished the way it is now, but what used to be really obvious (especially to someone who has always run dual boot set-ups), that you can boot an earlier kernel, is now an obscure piece of knowledge. Suggestions: 1. The grub boot screen should have an explicit message to this effect. 2. (More difficult to implement), autodetect failures to boot and explicitly offer the user the alternatives. (A la Windows, not everything they do is bad.) I think there's a way to install a one-time only grub configuration file, for the next boot. I'm not sure how it's done now, but I think suspend to disk worked this way before, to have grub boot some loader that restores the suspended image into ram. If restore failed, the next boot loaded the usual kernel. The kernel update can do that, and a start up script that runs at the end of the boot cycle then commit the permanent configuration file, at the tail end of the next boot. pgpX7Il87xAs5.pgp Description: PGP signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Latest Kernel causes reboot hell
2009/12/7 Sam Varshavchik : >> >> "The best way to avoid the problem might be to get grub to display the >> list of installed (assuming that the original F12 kernel worked for you) >> and select that kernel to boot from. Change the default line >> in /etc/grub.conf to automate that." Precisely, though there's no 'might' about it. Updated kernel fails to boot = boot to previous kernel instead. This is one of the easier update problems to work around, except that: > > It just occured to me that there may be a large number of people who are > completely unaware of the fact that they can easily boot a previous kernel. > > Some time ago, someone decided to set up grub by default to hide its boot > menu, so that it boots without delay. As such, some people may not even know > about this option. > > This is a perfect example of why hiding some complexity from the end user is > not always a good idea. > Yes, it does look more polished the way it is now, but what used to be really obvious (especially to someone who has always run dual boot set-ups), that you can boot an earlier kernel, is now an obscure piece of knowledge. Suggestions: 1. The grub boot screen should have an explicit message to this effect. 2. (More difficult to implement), autodetect failures to boot and explicitly offer the user the alternatives. (A la Windows, not everything they do is bad.) -- imalone -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Latest Kernel causes reboot hell
On Mon, 07 Dec 2009 18:30:02 -0500 Sam Varshavchik wrote: > Chris writes: > > > On Mon, 07 Dec 2009 18:06:12 -0500 > > Sam Varshavchik wrote: > > > >> Some time ago, in F9-F10 era, there was a consecutive series of > >> about four kernels that were released that could not boot on one > >> of my machines. Somehow, I managed to survive this traumatic > >> experience without installing a completely different distribution. > >> I waved a magic wand, and continued to boot the last working > >> kernel, until a new one came out that worked on my hardware once > >> more. > > > > I agree - quoting from Louis Lagendijk; > > > > "The best way to avoid the problem might be to get grub to display > > the list of installed (assuming that the original F12 kernel worked > > for you) and select that kernel to boot from. Change the default > > line in /etc/grub.conf to automate that." > > It just occured to me that there may be a large number of people who > are completely unaware of the fact that they can easily boot a > previous kernel. > > Some time ago, someone decided to set up grub by default to hide its > boot menu, so that it boots without delay. As such, some people may > not even know about this option. > > This is a perfect example of why hiding some complexity from the end > user is not always a good idea. > Thanks for the suggestions to all that helped me out. I am now past the kernel/reboot issue. -- Best regards, Chris “It is always better to have no ideas than false ones; to believe nothing, than to believe what is wrong.” -- Thomas Jefferson -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F12 Wireless disabled with kernel 2.6.31.6-162
John W. Linville-2 wrote: > > On Mon, Dec 07, 2009 at 09:32:01PM -0800, Richard England wrote: >> pro/wireless 2200BG in a Dell Latitude D410. F12 Fully updated (as of 7 >> December). >> >> With Kernel 2.6.31.6-162.fc12.i686 the wireless is completely >> disabled. This was the latest kernel installed. >> >> Backing down to kernel 2.6.31.6-145.fc12.i686 everything returns to >> normal. This was the immediately preceding kernel I had. >> >> Any one confirm this? I looked for a BZ entry but I'm notoriously bad >> at finding things there > > I'm running F12 on an T41 equipped with ipw2200. Perhaps you could > describe the problem more thoroughly (and/or open a bugzilla entry)? > > I have iwl4965 running fine with the same kernel in a Dell M4300 - -- View this message in context: http://old.nabble.com/F12-Wireless-disabled-with-kernel-2.6.31.6-162-tp26688966p26695103.html Sent from the Fedora List mailing list archive at Nabble.com. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F12 Wireless disabled with kernel 2.6.31.6-162
On Mon, Dec 07, 2009 at 09:32:01PM -0800, Richard England wrote: > pro/wireless 2200BG in a Dell Latitude D410. F12 Fully updated (as of 7 > December). > > With Kernel 2.6.31.6-162.fc12.i686 the wireless is completely > disabled. This was the latest kernel installed. > > Backing down to kernel 2.6.31.6-145.fc12.i686 everything returns to > normal. This was the immediately preceding kernel I had. > > Any one confirm this? I looked for a BZ entry but I'm notoriously bad > at finding things there I'm running F12 on an T41 equipped with ipw2200. Perhaps you could describe the problem more thoroughly (and/or open a bugzilla entry)? John -- John W. LinvilleLinux should be at the core linvi...@redhat.com of your literate lifestyle. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: kernel-2.6.31.6-162.fc12.x86_64 causes kernel panic
On Mon, Dec 7, 2009 at 10:26 PM, Sam Sharpe wrote: >> Have you noticed this bug >> >> https://bugzilla.redhat.com/show_bug.cgi?id=545043 > > Nope. Just updated and rebooted to check: > > [...@samlap ~]$ uname -a > Linux samlap.fireburst.co.uk 2.6.31.6-162.fc12.x86_64 #1 SMP Fri Dec 4 > 00:06:26 EST 2009 x86_64 x86_64 x86_64 GNU/Linux > > Funny modules loaded? Failure of dracut to build a correct initrd? Run > out of space on /boot? > > [...@samlap ~]$ ls -al /boot/*162* > -rw-r--r-- 1 root root 97986 2009-12-04 05:19 > /boot/config-2.6.31.6-162.fc12.x86_64 > -rw-r--r-- 1 root root 11286959 2009-12-07 22:17 > /boot/initramfs-2.6.31.6-162.fc12.x86_64.img > -rw-r--r-- 1 root root 1870388 2009-12-04 05:19 > /boot/System.map-2.6.31.6-162.fc12.x86_64 > -rwxr-xr-x 1 root root 3423712 2009-12-04 05:19 > /boot/vmlinuz-2.6.31.6-162.fc12.x86_64 Thanks, Sam. On a different computer, I do not get the reported kernel panic. Paul -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
F12 Wireless disabled with kernel 2.6.31.6-162
pro/wireless 2200BG in a Dell Latitude D410. F12 Fully updated (as of 7 December). With Kernel 2.6.31.6-162.fc12.i686 the wireless is completely disabled. This was the latest kernel installed. Backing down to kernel 2.6.31.6-145.fc12.i686 everything returns to normal. This was the immediately preceding kernel I had. Any one confirm this? I looked for a BZ entry but I'm notoriously bad at finding things there -- /~~R/ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Ath9 regression in latest kernel? SOLVED?
On Mon, 2009-12-07 at 14:58 -0600, Michael Cronenworth wrote: > Patrick O'Callaghan on 12/07/2009 02:24 PM wrote: > > Had anyone else seen this? I'll BZ if > > necessary. > > https://bugzilla.redhat.com/show_bug.cgi?id=538792 > > Upstream says to use the latest version of the driver as they won't > backport changes. The latest version of the driver still doesn't work > well. I pointed out a few git commits but they were ignored. > I compiled the latest driver from http://linuxwireless.org/en/users/Download and so far it's working extremely well (it's very modular so you don't have to recompile the kernel; the instructions on the page are very clear). I wouldn't normally do this but the alternative is to have a very painful net experience. I hope this updated version shows up soon in the official repos. poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Latest Kernel causes reboot hell
On Mon, 2009-12-07 at 11:37 -0800, Marc Wilson wrote: > There, that's MY snarky remark. > > Gods, people, if you want to use Ubuntu, go use Ubuntu already... no > need to tell everyone about it. Here's mine: He's taking his bat, and someone else's ball, and going home... -- [...@localhost ~]$ uname -r 2.6.27.25-78.2.56.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 Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Latest Kernel causes reboot hell
Chris writes: On Mon, 07 Dec 2009 18:06:12 -0500 Sam Varshavchik wrote: Some time ago, in F9-F10 era, there was a consecutive series of about four kernels that were released that could not boot on one of my machines. Somehow, I managed to survive this traumatic experience without installing a completely different distribution. I waved a magic wand, and continued to boot the last working kernel, until a new one came out that worked on my hardware once more. I agree - quoting from Louis Lagendijk; "The best way to avoid the problem might be to get grub to display the list of installed (assuming that the original F12 kernel worked for you) and select that kernel to boot from. Change the default line in /etc/grub.conf to automate that." It just occured to me that there may be a large number of people who are completely unaware of the fact that they can easily boot a previous kernel. Some time ago, someone decided to set up grub by default to hide its boot menu, so that it boots without delay. As such, some people may not even know about this option. This is a perfect example of why hiding some complexity from the end user is not always a good idea. pgp8BWvbdINKX.pgp Description: PGP signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Latest Kernel causes reboot hell
On Mon, 07 Dec 2009 18:06:12 -0500 Sam Varshavchik wrote: > Chris writes: > > > After running 12 for some weeks now, I allowed yum to install the > > newest kernel (well, as of Friday of course). > > > > all seemed to go just fine until I rebooted. All the machine will > > do is continue to reboot itself over and over again. > > > > I reinstalled and applied only updates other then 3 that were > > particular to the new kernel and all went well there. Rebooted just > > fine. > > > > I thought - why not try the remaining 3 and lets see if for some > > reason the others might be causing this effect. > > > > That didn't seem to help - again, after allowing yum to install the > > new kernel, it sent the machine into reboot hell. > > > > The box is only a few years (3) old, it's a Sony Vaio desktop. It's > > running sata, there is a /boot part of some 200 meg (only 23% full) > > and the rest of the 400 gig drive is LVM > > > > Currently, I tossed on Ubuntu just so I can get some work done > > however, would really prefer to be back running F12. > > > > Any help/ideas would be great. > > Some time ago, in F9-F10 era, there was a consecutive series of about > four kernels that were released that could not boot on one of my > machines. Somehow, I managed to survive this traumatic experience > without installing a completely different distribution. I waved a > magic wand, and continued to boot the last working kernel, until a > new one came out that worked on my hardware once more. > > I agree - quoting from Louis Lagendijk; "The best way to avoid the problem might be to get grub to display the list of installed (assuming that the original F12 kernel worked for you) and select that kernel to boot from. Change the default line in /etc/grub.conf to automate that." This seems to be the appropriate way for me to have handled it. Putting on another distro worked for me at the time. My home dir and data are on another sata drive so using a previously cloned image from Clonezilla got me up and running in under 10 mins when I needed to get some things done. Not meant to be long termed - but was a solution that I knew at the time. Fortunately (for me) I have a cloned-image of F12 from earlier in the week I'll put back on and use the above mentioned work around in addition to what you have said. I too recall the issues of F9/F10 (I touched on that with Louis in a private mail). In any event... Time to eat. -- Best regards, Chris -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Latest Kernel causes reboot hell
Chris writes: After running 12 for some weeks now, I allowed yum to install the newest kernel (well, as of Friday of course). all seemed to go just fine until I rebooted. All the machine will do is continue to reboot itself over and over again. I reinstalled and applied only updates other then 3 that were particular to the new kernel and all went well there. Rebooted just fine. I thought - why not try the remaining 3 and lets see if for some reason the others might be causing this effect. That didn't seem to help - again, after allowing yum to install the new kernel, it sent the machine into reboot hell. The box is only a few years (3) old, it's a Sony Vaio desktop. It's running sata, there is a /boot part of some 200 meg (only 23% full) and the rest of the 400 gig drive is LVM Currently, I tossed on Ubuntu just so I can get some work done however, would really prefer to be back running F12. Any help/ideas would be great. Some time ago, in F9-F10 era, there was a consecutive series of about four kernels that were released that could not boot on one of my machines. Somehow, I managed to survive this traumatic experience without installing a completely different distribution. I waved a magic wand, and continued to boot the last working kernel, until a new one came out that worked on my hardware once more. pgpoDt3aIEW0K.pgp Description: PGP signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: kernel-2.6.31.6-162.fc12.x86_64 causes kernel panic
2009/12/7 Paul Smith : > Dear All, > > Have you noticed this bug > > https://bugzilla.redhat.com/show_bug.cgi?id=545043 Nope. Just updated and rebooted to check: [...@samlap ~]$ uname -a Linux samlap.fireburst.co.uk 2.6.31.6-162.fc12.x86_64 #1 SMP Fri Dec 4 00:06:26 EST 2009 x86_64 x86_64 x86_64 GNU/Linux Funny modules loaded? Failure of dracut to build a correct initrd? Run out of space on /boot? [...@samlap ~]$ ls -al /boot/*162* -rw-r--r-- 1 root root97986 2009-12-04 05:19 /boot/config-2.6.31.6-162.fc12.x86_64 -rw-r--r-- 1 root root 11286959 2009-12-07 22:17 /boot/initramfs-2.6.31.6-162.fc12.x86_64.img -rw-r--r-- 1 root root 1870388 2009-12-04 05:19 /boot/System.map-2.6.31.6-162.fc12.x86_64 -rwxr-xr-x 1 root root 3423712 2009-12-04 05:19 /boot/vmlinuz-2.6.31.6-162.fc12.x86_64 -- Sam -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
kernel-2.6.31.6-162.fc12.x86_64 causes kernel panic
Dear All, Have you noticed this bug https://bugzilla.redhat.com/show_bug.cgi?id=545043 ? Thanks in advance, Paul -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Ath9 regression in latest kernel?
On Mon, 2009-12-07 at 15:57 -0500, Reuben D. Budiardja wrote: > On Monday 07 December 2009 15:24:59 Patrick O'Callaghan wrote: > > Since I updated to kernel-2.6.31.6-162.fc12.i686 on my EeePC 1000 > > netbook, Wifi has become so unreliable as to be virtually unusable. . > > > > The chipset is an AR928x. Had anyone else seen this? I'll BZ if > > necessary. > > Hello, > > Yes, I also asked this problem on this list last week. For your reference, > this is the thread: > http://marc.info/?l=fedora-list&m=125988446000571&w=2 > > Also, I observe that this workaround mentioned in one of bug reports (see > below) *seem* to give me better / more usable networking: > "iwconfig wlan0 power off" > YMMV. I did try that before backing out to the earlier kernel. It didn't seem to make any difference at all. > Here are several bug reports I bookmarked: > http://bugzilla.kernel.org/show_bug.cgi?id=13807 > http://bugzilla.kernel.org/show_bug.cgi?id=14267 > https://bugzilla.redhat.com/show_bug.cgi?id=532465 > https://bugzilla.redhat.com/show_bug.cgi?id=520535 > https://bugzilla.redhat.com/show_bug.cgi?id=541756 I'll take a look, thanks. poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Ath9 regression in latest kernel?
On Mon, 2009-12-07 at 12:41 -0800, Lonni J Friedman wrote: > On Mon, Dec 7, 2009 at 12:38 PM, Rick Stevens wrote: > > On 12/07/2009 12:24 PM, Patrick O'Callaghan wrote: > >> > >> Since I updated to kernel-2.6.31.6-162.fc12.i686 on my EeePC 1000 > >> netbook, Wifi has become so unreliable as to be virtually unusable. Lost > >> connections, dropped frames even when pinging the local AP, endless > >> browswer waits while "Resolving host ...". The same AP supports 1 iMac, > >> a Mac Mini, 3 laptops and about 6 iPhones, all with no problems, but I > >> reset it anyway just in case, to no effect. I've spent a couple of days > >> fraking around with NM before deciding to try rolling back to > >> kernel-2.6.31.6-145.fc12.i686, which immediately solved all the > >> problems. > >> > >> The chipset is an AR928x. Had anyone else seen this? I'll BZ if > >> necessary. > > > > Is the kernel the only thing that changed? Try booting an older one > > and see if the problem goes away. If it does, then yes, bugzilla it > > immediately. If an updated kernel breaks something as basic as > > networking, that makes it "necessary". :-) > > Yes, this is a known bug. It was even discussed on this list as > recently as last week. > I know, in fact I did look for it when the problem arose but couldn't pin down the thread. Apologies for repeating known material. poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Ath9 regression in latest kernel?
On Mon, 2009-12-07 at 12:38 -0800, Rick Stevens wrote: > On 12/07/2009 12:24 PM, Patrick O'Callaghan wrote: > > Since I updated to kernel-2.6.31.6-162.fc12.i686 on my EeePC 1000 > > netbook, Wifi has become so unreliable as to be virtually unusable. Lost > > connections, dropped frames even when pinging the local AP, endless > > browswer waits while "Resolving host ...". The same AP supports 1 iMac, > > a Mac Mini, 3 laptops and about 6 iPhones, all with no problems, but I > > reset it anyway just in case, to no effect. I've spent a couple of days > > fraking around with NM before deciding to try rolling back to > > kernel-2.6.31.6-145.fc12.i686, which immediately solved all the > > problems. > > > > The chipset is an AR928x. Had anyone else seen this? I'll BZ if > > necessary. > > Is the kernel the only thing that changed? Try booting an older one > and see if the problem goes away. As I said, I did that. The problem appears to have gone away (or at least retreated to a manageable level). > If it does, then yes, bugzilla it > immediately. If an updated kernel breaks something as basic as > networking, that makes it "necessary". :-) Looks like it's already there: https://bugzilla.redhat.com/show_bug.cgi?id=538792 poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Latest Kernel causes reboot hell
On 09-12-07 15:51:38, Kevin J. Cummings wrote: ... > I just went to reboot it. Since I wasn't logged into the console, I > used the GDM reboot button to reboot the system. While it was > shutting down, it just hung. That's when I noticed the caps-lock and > scroll-lock leds flashing in unison. Oh, cool, I thought, a kernel > panic! > > When it rebooted, it booted the new kernel: > kernel-2.6.31.6-162.fc12.i686 > > (I had been running kernel-2.6.31.6-145.fc12.i686 when it paniced). > > The machine booted OK for me. My surprise was when I went to look in > /var/log/messages, there was no mention of a kernel panic! > The last message was of smartd terminating. Followed by the reboot > of the new kernel. > > So, what happened? Did my system panic? If so, why no message in > /var/log/messages? If the panic was about the disk system then nothing will be written to the logs. Your only chance to see it is in a system console, before rebooting, and that's hard to do after the panic. -- TonyN.:' <mailto:tonynel...@georgeanelson.com> ' <http://www.georgeanelson.com/> -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Ath9 regression in latest kernel?
Patrick O'Callaghan on 12/07/2009 02:24 PM wrote: Had anyone else seen this? I'll BZ if necessary. https://bugzilla.redhat.com/show_bug.cgi?id=538792 Upstream says to use the latest version of the driver as they won't backport changes. The latest version of the driver still doesn't work well. I pointed out a few git commits but they were ignored. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Ath9 regression in latest kernel?
On Monday 07 December 2009 15:24:59 Patrick O'Callaghan wrote: > Since I updated to kernel-2.6.31.6-162.fc12.i686 on my EeePC 1000 > netbook, Wifi has become so unreliable as to be virtually unusable. . > > The chipset is an AR928x. Had anyone else seen this? I'll BZ if > necessary. Hello, Yes, I also asked this problem on this list last week. For your reference, this is the thread: http://marc.info/?l=fedora-list&m=125988446000571&w=2 Also, I observe that this workaround mentioned in one of bug reports (see below) *seem* to give me better / more usable networking: "iwconfig wlan0 power off" YMMV. Here are several bug reports I bookmarked: http://bugzilla.kernel.org/show_bug.cgi?id=13807 http://bugzilla.kernel.org/show_bug.cgi?id=14267 https://bugzilla.redhat.com/show_bug.cgi?id=532465 https://bugzilla.redhat.com/show_bug.cgi?id=520535 https://bugzilla.redhat.com/show_bug.cgi?id=541756 RDB -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Latest Kernel causes reboot hell
I just wanted to add my recent experience with the new F12 kernel A couple of days ago, I had a PF in my area (due to the snowstorm, I imagine). My F12 machine (the one *not* on a UPS, yet) remained down for a couple of days. This morning, noting last night's updates, I rebooted it (so I could update it!). I used ssh and updated over the network using yum. (I really wanted to see the "reboot hell".) B^) I just went to reboot it. Since I wasn't logged into the console, I used the GDM reboot button to reboot the system. While it was shutting down, it just hung. That's when I noticed the caps-lock and scroll-lock leds flashing in unison. Oh, cool, I thought, a kernel panic! When it rebooted, it booted the new kernel: kernel-2.6.31.6-162.fc12.i686 (I had been running kernel-2.6.31.6-145.fc12.i686 when it paniced). The machine booted OK for me. My surprise was when I went to look in /var/log/messages, there was no mention of a kernel panic! The last message was of smartd terminating. Followed by the reboot of the new kernel. So, what happened? Did my system panic? If so, why no message in /var/log/messages? -- Kevin J. Cummings kjch...@rcn.com cummi...@kjchome.homeip.net cummi...@kjc386.framingham.ma.us Registered Linux User #1232 (http://counter.li.org) -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Ath9 regression in latest kernel?
On Mon, Dec 7, 2009 at 12:38 PM, Rick Stevens wrote: > On 12/07/2009 12:24 PM, Patrick O'Callaghan wrote: >> >> Since I updated to kernel-2.6.31.6-162.fc12.i686 on my EeePC 1000 >> netbook, Wifi has become so unreliable as to be virtually unusable. Lost >> connections, dropped frames even when pinging the local AP, endless >> browswer waits while "Resolving host ...". The same AP supports 1 iMac, >> a Mac Mini, 3 laptops and about 6 iPhones, all with no problems, but I >> reset it anyway just in case, to no effect. I've spent a couple of days >> fraking around with NM before deciding to try rolling back to >> kernel-2.6.31.6-145.fc12.i686, which immediately solved all the >> problems. >> >> The chipset is an AR928x. Had anyone else seen this? I'll BZ if >> necessary. > > Is the kernel the only thing that changed? Try booting an older one > and see if the problem goes away. If it does, then yes, bugzilla it > immediately. If an updated kernel breaks something as basic as > networking, that makes it "necessary". :-) Yes, this is a known bug. It was even discussed on this list as recently as last week. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Ath9 regression in latest kernel?
On 12/07/2009 12:24 PM, Patrick O'Callaghan wrote: Since I updated to kernel-2.6.31.6-162.fc12.i686 on my EeePC 1000 netbook, Wifi has become so unreliable as to be virtually unusable. Lost connections, dropped frames even when pinging the local AP, endless browswer waits while "Resolving host ...". The same AP supports 1 iMac, a Mac Mini, 3 laptops and about 6 iPhones, all with no problems, but I reset it anyway just in case, to no effect. I've spent a couple of days fraking around with NM before deciding to try rolling back to kernel-2.6.31.6-145.fc12.i686, which immediately solved all the problems. The chipset is an AR928x. Had anyone else seen this? I'll BZ if necessary. Is the kernel the only thing that changed? Try booting an older one and see if the problem goes away. If it does, then yes, bugzilla it immediately. If an updated kernel breaks something as basic as networking, that makes it "necessary". :-) -- - Rick Stevens, Systems Engineer ri...@nerd.com - - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - -- - We are born naked, wet and hungry. Then things get worse. - -- -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Ath9 regression in latest kernel?
Since I updated to kernel-2.6.31.6-162.fc12.i686 on my EeePC 1000 netbook, Wifi has become so unreliable as to be virtually unusable. Lost connections, dropped frames even when pinging the local AP, endless browswer waits while "Resolving host ...". The same AP supports 1 iMac, a Mac Mini, 3 laptops and about 6 iPhones, all with no problems, but I reset it anyway just in case, to no effect. I've spent a couple of days fraking around with NM before deciding to try rolling back to kernel-2.6.31.6-145.fc12.i686, which immediately solved all the problems. The chipset is an AR928x. Had anyone else seen this? I'll BZ if necessary. poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Latest Kernel causes reboot hell
On Mon, 2009-12-07 at 20:07 +, Chris wrote: > >-Original Message- > >From: Marc Wilson [mailto:m...@cox.net] > >Sent: Monday, December 7, 2009 01:37 PM > >To: 'Community assistance, encouragement,and advice for using Fedora.' > >Subject: Re: Latest Kernel causes reboot hell > > > >On Mon, Dec 7, 2009 at 10:44 AM, Chris wrote: > > > >> Currently, I tossed on Ubuntu just so I can get some work done however, > >> would really prefer to be back running F12. > > > >Other than that it let you make a snarky Ubuntu remark, why would you > >need to replace F12 "just so that you can get some work done"? It > >would seem obvious that all you have to do is not perform the latest > >upgrade until whatever happened to it gets fixed. > > > >Oh, wait... that would't let you version-chase. After all, apparently > >software with lower version numbers magically ceases to work. > > > >There, that's MY snarky remark. > > > >Gods, people, if you want to use Ubuntu, go use Ubuntu already... no > >need to tell everyone about it. > > *IF* I really wanted to make a "snarky" remark I would have inserted > something more appropriate like windows however, I thought my question was > certainly genuine enough. > > As I did mention in the post - I did exactly that, I updated all but the > kernel stuff (second time around) and mentioned that all worked well. Then, > simply stated that the newest kernel seems to have caused a break (in my > system at least) and felt I might say something to see if anyone else had the > same experience, and if they did - how did they rectify it. > > I apologize to you, Marc, if me question infuriated you to the point to get > upset. I have to believe that others didn't see it the same fashion as you. Chris, I think your question was correct. The best way to avoid the problem might be to get grub to display the list of installed (assuming that the original F12 kernel worked for you) and select that kernel to boot from. Change the default line in /etc/grub.conf to automate that. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Latest Kernel causes reboot hell
>-Original Message- >From: Marc Wilson [mailto:m...@cox.net] >Sent: Monday, December 7, 2009 01:37 PM >To: 'Community assistance, encouragement, and advice for using Fedora.' >Subject: Re: Latest Kernel causes reboot hell > >On Mon, Dec 7, 2009 at 10:44 AM, Chris wrote: > >> Currently, I tossed on Ubuntu just so I can get some work done however, >> would really prefer to be back running F12. > >Other than that it let you make a snarky Ubuntu remark, why would you >need to replace F12 "just so that you can get some work done"? It >would seem obvious that all you have to do is not perform the latest >upgrade until whatever happened to it gets fixed. > >Oh, wait... that would't let you version-chase. After all, apparently >software with lower version numbers magically ceases to work. > >There, that's MY snarky remark. > >Gods, people, if you want to use Ubuntu, go use Ubuntu already... no >need to tell everyone about it. *IF* I really wanted to make a "snarky" remark I would have inserted something more appropriate like windows however, I thought my question was certainly genuine enough. As I did mention in the post - I did exactly that, I updated all but the kernel stuff (second time around) and mentioned that all worked well. Then, simply stated that the newest kernel seems to have caused a break (in my system at least) and felt I might say something to see if anyone else had the same experience, and if they did - how did they rectify it. I apologize to you, Marc, if me question infuriated you to the point to get upset. I have to believe that others didn't see it the same fashion as you. Regards, Chris -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Latest Kernel causes reboot hell
On Mon, Dec 7, 2009 at 10:44 AM, Chris wrote: > Currently, I tossed on Ubuntu just so I can get some work done however, would > really prefer to be back running F12. Other than that it let you make a snarky Ubuntu remark, why would you need to replace F12 "just so that you can get some work done"? It would seem obvious that all you have to do is not perform the latest upgrade until whatever happened to it gets fixed. Oh, wait... that would't let you version-chase. After all, apparently software with lower version numbers magically ceases to work. There, that's MY snarky remark. Gods, people, if you want to use Ubuntu, go use Ubuntu already... no need to tell everyone about it. -- Marc Wilson m...@cox.net -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Latest Kernel causes reboot hell
After running 12 for some weeks now, I allowed yum to install the newest kernel (well, as of Friday of course). all seemed to go just fine until I rebooted. All the machine will do is continue to reboot itself over and over again. I reinstalled and applied only updates other then 3 that were particular to the new kernel and all went well there. Rebooted just fine. I thought - why not try the remaining 3 and lets see if for some reason the others might be causing this effect. That didn't seem to help - again, after allowing yum to install the new kernel, it sent the machine into reboot hell. The box is only a few years (3) old, it's a Sony Vaio desktop. It's running sata, there is a /boot part of some 200 meg (only 23% full) and the rest of the 400 gig drive is LVM Currently, I tossed on Ubuntu just so I can get some work done however, would really prefer to be back running F12. Any help/ideas would be great. TIA Chris -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: suggested upgrade path from fc8 to fc12 *OR* isolated kernel upgrade from 2.6.23 to 2.6.32
On Sun, Dec 06, 2009 at 23:05:06 -0500, Sam Varshavchik wrote: > > I think that happened before F8, but you need to double check. If > this happened in F9, I would suggest piecemeal updates. I'm sure you > will still easily find F9 images to download and install, the after > updating to F9 (presuming that's the release that switched to the > new RPM DB format), jump to F12. He isn't going to be able to go directly from F8 to F12 without a lot of futzing around. A fresh install might be less work. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: suggested upgrade path from fc8 to fc12 *OR* isolated kernel upgrade from 2.6.23 to 2.6.32
sting writes: I'm on fedora core 8, and I may have a need to upgrade to the latest, v12, because of an issue I'm encountering (described in "some background", below, but my main query is here). Essentially, I'm going to have to either upgrade frin fc8 to fc12 or perform an isolated kernel upgrade from 2.6.23 to 2.6.32 (that may not be without issues). Given a choice between trying to built the current kernel and cram it into such an old distro, versus updating Fedora 8 to Fedora 12, I would choose an upgrade to Fedora 12, without hesitating. 1. If there are any chances that kernel compatibility with certain userland tools could be broken (once the kernel is correctly booting, that is) given the "large" version jump from 2.6.23 to 2.6.32 (might as well update to latest). For example, would some commands for traffic control (tc) not work anymore? Historically, both the Linux kernel and glibc have a very good track record for backwards compatibility. However, upgrading the entire distro will, of course, end up upgrading your tc binary. Whether or not the tc binary in Fedora 12 is backwards compatible, in all respects, with tc in Fedora 8 is something that I do not know. You can grab the man page for tc in Fedora 12, compare it with what you have in Fedora 8, and draw your own conclusions. 2. If it actually would be simpler & safer to just upgrade the distribution? (as long as the paths to the various network scripts haven't changed, mostly around interfaces, VLANs, etc) I'm fairly sure that some of these things have changed. And I'm also quite sure that dealing with that is much easier than dealing with building your own kernel and cramming it into an older distro. In terms of keeping the various tools on the machine compatible with the kernel, I am tempted to go with #2. However, how safe is it to jump directly from fedora core 8 to fedora core 12? I guess most upgrades are tested from FC version N to N+1. I would jump 4 versions directly. Correct. Such upgrade paths are not tested by anyone. I have, previously, upgraded from N to N+2 without any issues. I just did it again, upgrading from F10 to F12 (because I could not upgrade to F11 due to a bug in F11's anaconda). Your probability of success depends solely on how well you've cared for your existing F8 system. If you did not mess with it, if you only installed software using RPM, and used the system's configuration tools, where available, or kept manual editing of various config files to a minimum, you shouldn't have any problems. On the other hand, if you hand-compiled a bunch of stuff; if you routinely grabbed various random tarballs, and went the configure/make/make-install route, spraying untracked files and dependencies all over the filesystem, rather than building proper RPMs, you'll likely to have a major mess on your hands after an upgrade. I do recall that, some time ago, there was a major upgrade to the RPM database format -- a switch to a new major version of the DB back end. Anaconda, on the upgrade path, took care of converting the old format to the new one. I think that happened before F8, but you need to double check. If this happened in F9, I would suggest piecemeal updates. I'm sure you will still easily find F9 images to download and install, the after updating to F9 (presuming that's the release that switched to the new RPM DB format), jump to F12. In either case, after updating to F12, you will need to run 'updatedb', then use 'locate' to find all 'rpmsave' and 'rpmnew' configuration files the upgrade process introduced, then manually reconcile them with the active configuration files. That should be the extent of the manual effort involved in upgrading to F12 from an older version. pgpe3YrngfxAv.pgp Description: PGP signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
suggested upgrade path from fc8 to fc12 *OR* isolated kernel upgrade from 2.6.23 to 2.6.32
I'm on fedora core 8, and I may have a need to upgrade to the latest, v12, because of an issue I'm encountering (described in "some background", below, but my main query is here). Essentially, I'm going to have to either upgrade frin fc8 to fc12 or perform an isolated kernel upgrade from 2.6.23 to 2.6.32 (that may not be without issues). If I understand the issue I'm having correctly, what will fix it is a kernel ugprade. I've attempted to upgrade the kernel to latest (2.6.31 at the time) but I've run into some problems that will require troubleshooting, and given that I extremely rarely upgrade kernels, it could take me a while (fwiw, I tried the kernel ugprade on a vmware instance, don't know if that can lead to kernel upgrade problems that I otherwise wouldn't have). So before going down that path, I would like to know: 1. If there are any chances that kernel compatibility with certain userland tools could be broken (once the kernel is correctly booting, that is) given the "large" version jump from 2.6.23 to 2.6.32 (might as well update to latest). For example, would some commands for traffic control (tc) not work anymore? 2. If it actually would be simpler & safer to just upgrade the distribution? (as long as the paths to the various network scripts haven't changed, mostly around interfaces, VLANs, etc) In terms of keeping the various tools on the machine compatible with the kernel, I am tempted to go with #2. However, how safe is it to jump directly from fedora core 8 to fedora core 12? I guess most upgrades are tested from FC version N to N+1. I would jump 4 versions directly. For what it's worth, I have an image of the machine running on vmware, so I could attempt the ugprade there first. Any suggestions as to which path I should take? Isolated kernel upgrade or upgrade the distribution? Thanks, sting Big PS: (if you care about the context) We use a fedora core 8 box as a router, mostly to shape traffic for network simulation purposes. We have many projects (games or games-related, actually) that use real-time network communication, and employ various network models. Via the use of VLANs, we allow for machines anywhere in our studio to hop on this router, at which point we apply selective traffic shaping rules. So, we have a large number of interfaces (due to the large number of VLANs), and in order to shape traffic bidirectionally, we also use the ifb device which adds even more interfaces. So: - We have lots of interfaces: 52 (26 VLAN interfaces, 26 equivalent ifb interfaces) - We mostly use the token buffer filter (tbf) and netem queueing disciplines - We use the mirroring action to redirect ingress traffic from the regular VLAN interfaces to the IFB devices Every now and then, when replacing/removing/adding qdiscs on the fly (and I think it only happens when a tbf qdiscs is involved), the kernel locks. No crash, just a lock, seemingly stuck in an endless loop. There seems to have been some work done on around endless loops in the kernel network scheduler around nov 2006. Kernel 2.6.23 (which I have) was released around sept 2007. Maybe it takes that long to promote some changes from dev to release. Hopefully that's what I'm hitting. And hopefully by doing a kernel upgrade it will go away. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
