Re: kernel module
2010/1/9 Luca lucar...@gmail.com: 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
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 linuxguy...@gmail.com: 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 ?
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 linuxguy...@gmail.com: 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 ?
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 linuxguy...@gmail.com: 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, 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 linuxguy...@gmail.com: 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 ?
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 linuxguy...@gmail.com: 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 ?
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 ?
2010/1/6 Linuxguy123 linuxguy...@gmail.com: 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 ?
2010/1/6 Linuxguy123 linuxguy...@gmail.com: 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
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 security update required or not?
On Mon, Dec 21, 2009 at 11:33:23AM +1100, Bojan Smojver wrote: According to this: http://lwn.net/Articles/367443/, latest kernel updates have security fixes (the second one appears on the 2.6.31.9 list). Is this something that has been backported to current F-12 kernels (I don't see it in changelog), or do we need a security update for F-12 here? Sorry, I forgot to push it to bodhi after the build completed (blame ppc, it takes far too long.) They should be pushed now (with an extra fix to fuse.) In the future, if you want to ask such questions, fedora-kernel-list would be much more appropriate. I for one, don't have time to read fedora-devel-list often. regards, Kyle. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel security update required or not?
On Tue, Dec 22, 2009 at 10:56:26 -0500, Clyde E. Kunkel clydekunkel7...@cox.net wrote: does adding nomodeset to kernel parm line in grub.conf work? It gets me back to the other problem. So yeah it does seem like we are seeing the same thing. I update the bug to mention this. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel security update required or not?
2009/12/21 Bojan Smojver bo...@rexursive.com: On Sun, 2009-12-20 at 22:21 -0600, Bruno Wolff III wrote: I didn't see any of the recent previous spec file comments indicate back ported security fixes. So its unlikely the latest security fixes are in any earlier version. If you want them now, grab the kernel from koji. Otherise you can wait for the kernel to push to updates or updates-testing depending on how much you want to wait for other people to test it before you try it out. I understand what I can do. That is not the issue. The question is, should Fedora get a security update or not - you know - for all the users out there that are unaware of Koji etc. I'm sure Fedora kernel folks reading the list will know. Ask on Fedora-kernel. Its got a better SNR and you don't need to subscribe. -- Christopher Brown -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel security update required or not?
On 12/20/2009 11:16 PM, Bruno Wolff III wrote: On Sun, Dec 20, 2009 at 21:17:46 -0500, Mail Listsli...@sapience.com wrote: On 12/20/2009 08:34 PM, Bojan Smojver wrote: On Sun, 2009-12-20 at 19:16 -0600, Bruno Wolff III wrote: There is a 2.6.31.9 build in Koji. Yeah, I've seen it. But, it's not in updates. Hence the question. Sure wish 2.6.32 would come soon ... anyone know when ? Be careful what you wish for. 2.6.32 isn't working for me. I have to use 2.6.31 kernels from F12 on my otherwise rawhide system, to get it to boot. does adding nomodeset to kernel parm line in grub.conf work? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel security update required or not?
On Mon, Dec 21, 2009 at 11:33:23 +1100, Bojan Smojver bo...@rexursive.com wrote: According to this: http://lwn.net/Articles/367443/, latest kernel updates have security fixes (the second one appears on the 2.6.31.9 list). Is this something that has been backported to current F-12 kernels (I don't see it in changelog), or do we need a security update for F-12 here? There is a 2.6.31.9 build in Koji. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel security update required or not?
On Sun, 2009-12-20 at 19:16 -0600, Bruno Wolff III wrote: There is a 2.6.31.9 build in Koji. Yeah, I've seen it. But, it's not in updates. Hence the question. -- Bojan -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel security update required or not?
On 12/20/2009 08:34 PM, Bojan Smojver wrote: On Sun, 2009-12-20 at 19:16 -0600, Bruno Wolff III wrote: There is a 2.6.31.9 build in Koji. Yeah, I've seen it. But, it's not in updates. Hence the question. Sure wish 2.6.32 would come soon ... anyone know when ? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel security update required or not?
On Sun, Dec 20, 2009 at 21:17:46 -0500, Mail Lists li...@sapience.com wrote: On 12/20/2009 08:34 PM, Bojan Smojver wrote: On Sun, 2009-12-20 at 19:16 -0600, Bruno Wolff III wrote: There is a 2.6.31.9 build in Koji. Yeah, I've seen it. But, it's not in updates. Hence the question. Sure wish 2.6.32 would come soon ... anyone know when ? Be careful what you wish for. 2.6.32 isn't working for me. I have to use 2.6.31 kernels from F12 on my otherwise rawhide system, to get it to boot. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel security update required or not?
On Mon, Dec 21, 2009 at 12:34:06 +1100, Bojan Smojver bo...@rexursive.com wrote: On Sun, 2009-12-20 at 19:16 -0600, Bruno Wolff III wrote: There is a 2.6.31.9 build in Koji. Yeah, I've seen it. But, it's not in updates. Hence the question. I didn't see any of the recent previous spec file comments indicate back ported security fixes. So its unlikely the latest security fixes are in any earlier version. If you want them now, grab the kernel from koji. Otherise you can wait for the kernel to push to updates or updates-testing depending on how much you want to wait for other people to test it before you try it out. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel security update required or not?
On Sun, 2009-12-20 at 22:21 -0600, Bruno Wolff III wrote: I didn't see any of the recent previous spec file comments indicate back ported security fixes. So its unlikely the latest security fixes are in any earlier version. If you want them now, grab the kernel from koji. Otherise you can wait for the kernel to push to updates or updates-testing depending on how much you want to wait for other people to test it before you try it out. I understand what I can do. That is not the issue. The question is, should Fedora get a security update or not - you know - for all the users out there that are unaware of Koji etc. I'm sure Fedora kernel folks reading the list will know. -- Bojan -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel security update required or not?
On Mon, Dec 21, 2009 at 16:02:20 +1100, Bojan Smojver bo...@rexursive.com wrote: I understand what I can do. That is not the issue. The question is, should Fedora get a security update or not - you know - for all the users out there that are unaware of Koji etc. I'm sure Fedora kernel folks reading the list will know. Should they all get a potentially broken kernel? The risk of known vulnerabilities that are purported to be fixed, needs to balanced against the risk that there are regressions in the kernel. It's pretty normal for local root fixes not to get pushed out for a week or so, to give time for some testing. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel security update required or not?
On Sun, 2009-12-20 at 23:41 -0600, Bruno Wolff III wrote: Should they all get a potentially broken kernel? The risk of known vulnerabilities that are purported to be fixed, needs to balanced against the risk that there are regressions in the kernel. This is what Fedora kernel developers do, yes. It's pretty normal for local root fixes not to get pushed out for a week or so, to give time for some testing. Ditto. -- Bojan -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: kernel/accounting question ...
On 10/19/2006 08:23 AM, William W. Austin wrote: Not that I've got an answer for your question, but you might want to tell your computer that it's not 2006. -- Peter When privacy is outlawed only outlaws will have privacy. -- Zimmermann -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: kernel/accounting question ...
On Thu, 19 Oct 2006 08:23:49 -0400 William W. Austin waus...@speakeasy.net wrote: (I know that this question might be more reasonable on a kernel list, but a while back I posted the question twice and got no answers.) Possibly because the system you are sending email from thinks it's 2006, so many people wouldn't notice your old post if they are sorting by date? snip question Fix your date and try the kernel list again? kevin signature.asc Description: PGP signature -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: kernel/accounting question ...
Peter Jones wrote: Not that I've got an answer for your question, but you might want to tell your computer that it's not 2006. William W. Austin (or possibly his ISP, Speakeasy) is actually resending mail which was originally sent back in 2006. I got 2 extra copies of a mail I already received back in 2006. Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: kernel error message from pulseaudio
2009/12/14 Paolo Galtieri pgalti...@gmail.com: 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
Re: kernel update highly recommended
On 12/09/2009 11:14 AM, Kyle McMartin wrote: Hi folks, I'd highly recommend if you're running 2.6.31 or 2.6.32, that you update to the latest kernel in the koji builds here: http://koji.fedoraproject.org/koji/taskinfo?taskID=1864871 http://koji.fedoraproject.org/koji/taskinfo?taskID=1864876 They fix a rather severe security problem with ext4 caused by insufficient permission checking by the ext4 ioctl code, allowing a malicious local user to corrupt files. Note, the ioctl isn't currently used by userspace, so if you build your own kernels, you can just nuke the entire EXT4_IOC_MOVE_EXT ioctl case. NOTE: This is only a problem if you're using EXT4, if you aren't, you're safe. I'll get these pushed out to stable asap, but I wanted to let folks know just in case rawhide doesn't compose before the downtime. This a rawhide only issue or F12 as well? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: kernel update highly recommended
On Wed, Dec 09, 2009 at 11:20:02 -0700, Nathanael D. Noblet nathan...@gnat.ca wrote: This a rawhide only issue or F12 as well? It affects F12. You want the -166 kernel. However right now it is still building. (I didn't check to see if some arches are done already.) The updated kernel for rawhide has completed building. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: kernel update highly recommended
On Wed, Dec 09, 2009 at 12:23:50 -0600, Bruno Wolff III br...@wolff.to wrote: On Wed, Dec 09, 2009 at 11:20:02 -0700, Nathanael D. Noblet nathan...@gnat.ca wrote: This a rawhide only issue or F12 as well? It affects F12. You want the -166 kernel. However right now it is still building. (I didn't check to see if some arches are done already.) The updated kernel for rawhide has completed building. The 686 step is not quite done yet, but eveything else is. You can grab the rpms that are done by walking down into the tasks. The build will probably be done in a few minutes though. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: kernel update highly recommended
2009/12/9 Kyle McMartin k...@mcmartin.ca: NOTE: This is only a problem if you're using EXT4, if you aren't, you're safe. ReiserFS FTW!!! :) -- Christopher Brown -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: kernel-2.6.31.6-162.fc12.x86_64 causes kernel panic
On Mon, Dec 7, 2009 at 10:26 PM, Sam Sharpe lists.red...@samsharpe.net 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
Re: kernel-2.6.31.6-162.fc12.x86_64 causes kernel panic
2009/12/7 Paul Smith phh...@gmail.com: 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
Re: Kernel-2.6.31.6-134 seems to have a bug on R600 DRM
interestingly i just updated a radeon hd4650 box to latest rawhide and the same error pops up again: [drm:r600_cs_packet_next_reloc_mm] *ERROR* No packet3 for relocation for packet at 45. [drm:r600_packet3_check] *ERROR* bad SET_CONTEXT_REG 0x28014 [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! kind regards, Rudolf Kastl -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel-2.6.31.6-134 seems to have a bug on R600 DRM
2009/11/23 Otto Haliburton ottohalibur...@tx.rr.com: - Original Message - From: Adam Williamson awill...@redhat.com To: Development discussions related to Fedora fedora-devel-list@redhat.com Sent: Monday, November 23, 2009 3:03 PM Subject: Re: Kernel-2.6.31.6-134 seems to have a bug on R600 DRM On Mon, 2009-11-23 at 12:44 +0100, Andreas Tunek wrote: I seem to get crashes when I sometimes close tabs in Epiphany of Firefox. I have a ATI Mobile 340 (based on the R100 series I think). I do not get the same error on my other computer with intel gfx. That has absolutely nothing to do with what Liang posted, but please do file a separate bug report for it: https://fedoraproject.org/wiki/How_to_debug_Xorg_problems thanks! again criticizing the reporter for reporting his case. That was what he was doing when it crashed, he might not know that it is unrelated, but just reporting what he was doing at the time of the crash. I did not feel very criticized :) I should file a bug, I just haven't got around to it yet. Maybe tonight :) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel-2.6.31.6-134 seems to have a bug on R600 DRM
Thanks, everyone. I update to kernel-2.6.31.6-148, compiz and gnome-shell return to normal. I think that I should write a post after searching the FP wiki for radeon and KMS, Liang -- urlhttp://www.liangsuilong.info/url Fight for freedom(3F） Ask not what your Linux distro can do for you! Ask what you can do for your Linux distro! -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
RE: Kernel failure while writing DVD-RAM
On Wed, 2009-11-18 at 10:43 +, Dave Higton wrote: Hello Dave, Sorry for the late reply. Somehow missed you message due to excessive F12-release noise. :) OK. I've just been Googling for warn_slowpath, but although I've found lots of examples, I don't know what it means. My guess is that it's used as a diagnostic by some code, probably kernel code, so the next challenge is to find where it was called from. Yes? I tried tracking down the kernel code... Are you getting a real crash or some kind of failure. More information since my original posting: fillDVD2 is a test app that I wrote as part of an effort to test the ability of Fedora to write DVD-RAM discs. We have experienced numerous failures, but we don't yet understand why. fillDVD2 wasn't testing for errors. An error occurred somewhere, but fillDVD2 carried on trying to write to the DVD-RAM disc. This doesn't work; once DVD-RAM writing has failed, no subsequent attempts will succeed. The disc has to be ejected. I revised fillDVD2 to stop on an error. A subsequent test showed that the first error, at a similar point (when the disc was within a few hundred MB of getting full), was I/O error. Not very meaningful to me. Other than the WARN_ON, are you seeing anything useful in the kernel log? uname -a says: 2.6.27.38-170.2.113.fc10.i686 #1 SMP Wed Nov 4 17:55:39 EST 2009 i686 i686 i386 GNULinux We originally wanted to use CentOS but were never able to solve a real-time problem it gave us: we need to service interrupts from our cards every 32 ms. Normally the IRQ is active for no more than 8 us before it's serviced; under CentOS this would often exceed 20 ms and we would lose data. Weird. 8us sounds right under both RHEL and Fedora. Care to take it off ML? - Gilboa -- 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-134 seems to have a bug on R600 DRM
2009/11/23 Liang Suilong liangsuil...@gmail.com: After updating the package, compiz crashed and glxgears can not run. However, KMS and plymouth can still run well. Here is dmesg message that I grabbed: [drm:r600_cs_packet_next_reloc_mm] *ERROR* No packet3 for relocation for packet at 47. [drm:r600_packet3_check] *ERROR* bad SET_CONTEXT_REG 0x28014 [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! But I reboot with kernel-2.6.31.5-127. All the thing return to normal. My desktop is running on Fedora 12 x86_64. My graphic card is HD3650. ATi display drivers: xorg-x11-drv-ati-6.13.0-0.11.20091119git437113124.fc12 Kernel: 2.6.31.6-134.fc12.x86_64 Mesa: 7.6-0.15.fc12 Does any guy meet the same situation? -- urlhttp://www.liangsuilong.info/url Fight for freedom(3F） Ask not what your Linux distro can do for you! Ask what you can do for your Linux distro! I seem to get crashes when I sometimes close tabs in Epiphany of Firefox. I have a ATI Mobile 340 (based on the R100 series I think). I do not get the same error on my other computer with intel gfx. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel-2.6.31.6-134 seems to have a bug on R600 DRM
On Mon, 2009-11-23 at 12:44 +0100, Andreas Tunek wrote: I seem to get crashes when I sometimes close tabs in Epiphany of Firefox. I have a ATI Mobile 340 (based on the R100 series I think). I do not get the same error on my other computer with intel gfx. That has absolutely nothing to do with what Liang posted, but please do file a separate bug report for it: https://fedoraproject.org/wiki/How_to_debug_Xorg_problems thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel-2.6.31.6-134 seems to have a bug on R600 DRM
On Mon, 2009-11-23 at 17:31 +0800, Liang Suilong wrote: After updating the package, compiz crashed and glxgears can not run. However, KMS and plymouth can still run well. Here is dmesg message that I grabbed: [drm:r600_cs_packet_next_reloc_mm] *ERROR* No packet3 for relocation for packet at 47. [drm:r600_packet3_check] *ERROR* bad SET_CONTEXT_REG 0x28014 [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! But I reboot with kernel-2.6.31.5-127. All the thing return to normal. My desktop is running on Fedora 12 x86_64. My graphic card is HD3650. can you check if this is still the case with 145, and make sure you're also running updated mesa packages from koji? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel-2.6.31.6-134 seems to have a bug on R600 DRM
- Original Message - From: Adam Williamson awill...@redhat.com To: Development discussions related to Fedora fedora-devel-list@redhat.com Sent: Monday, November 23, 2009 3:03 PM Subject: Re: Kernel-2.6.31.6-134 seems to have a bug on R600 DRM On Mon, 2009-11-23 at 12:44 +0100, Andreas Tunek wrote: I seem to get crashes when I sometimes close tabs in Epiphany of Firefox. I have a ATI Mobile 340 (based on the R100 series I think). I do not get the same error on my other computer with intel gfx. That has absolutely nothing to do with what Liang posted, but please do file a separate bug report for it: https://fedoraproject.org/wiki/How_to_debug_Xorg_problems thanks! again criticizing the reporter for reporting his case. That was what he was doing when it crashed, he might not know that it is unrelated, but just reporting what he was doing at the time of the crash. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel-2.6.31.6-134 seems to have a bug on R600 DRM
On Mon, 2009-11-23 at 13:03 -0800, Adam Williamson wrote: On Mon, 2009-11-23 at 17:31 +0800, Liang Suilong wrote: After updating the package, compiz crashed and glxgears can not run. However, KMS and plymouth can still run well. Here is dmesg message that I grabbed: [drm:r600_cs_packet_next_reloc_mm] *ERROR* No packet3 for relocation for packet at 47. [drm:r600_packet3_check] *ERROR* bad SET_CONTEXT_REG 0x28014 [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! But I reboot with kernel-2.6.31.5-127. All the thing return to normal. My desktop is running on Fedora 12 x86_64. My graphic card is HD3650. can you check if this is still the case with 145, and make sure you're also running updated mesa packages from koji? -145 should fix this, a patch went in upstream that we didn't want in F-12, I had to remember to revert it. I should push out a new mesa before we can ship that fix. Dave. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel-2.6.31.6-134 seems to have a bug on R600 DRM
On Mon, 2009-11-23 at 16:52 -0600, Otto Haliburton wrote: - Original Message - From: Adam Williamson awill...@redhat.com To: Development discussions related to Fedora fedora-devel-list@redhat.com Sent: Monday, November 23, 2009 3:03 PM Subject: Re: Kernel-2.6.31.6-134 seems to have a bug on R600 DRM On Mon, 2009-11-23 at 12:44 +0100, Andreas Tunek wrote: I seem to get crashes when I sometimes close tabs in Epiphany of Firefox. I have a ATI Mobile 340 (based on the R100 series I think). I do not get the same error on my other computer with intel gfx. That has absolutely nothing to do with what Liang posted, but please do file a separate bug report for it: https://fedoraproject.org/wiki/How_to_debug_Xorg_problems thanks! again criticizing the reporter for reporting his case. That was what he was Um, where did I criticize anyone? I just told the reporter it wasn't the same bug. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
RE: Kernel-2.6.31.6-134 seems to have a bug on R600 DRM
-Original Message- From: fedora-devel-list-boun...@redhat.com [mailto:fedora-devel-list- boun...@redhat.com] On Behalf Of Adam Williamson Sent: Monday, November 23, 2009 20:20 To: Development discussions related to Fedora Subject: Re: Kernel-2.6.31.6-134 seems to have a bug on R600 DRM On Mon, 2009-11-23 at 16:52 -0600, Otto Haliburton wrote: - Original Message - From: Adam Williamson awill...@redhat.com To: Development discussions related to Fedora fedora-devel-list@redhat.com Sent: Monday, November 23, 2009 3:03 PM Subject: Re: Kernel-2.6.31.6-134 seems to have a bug on R600 DRM On Mon, 2009-11-23 at 12:44 +0100, Andreas Tunek wrote: I seem to get crashes when I sometimes close tabs in Epiphany of Firefox. I have a ATI Mobile 340 (based on the R100 series I think). I do not get the same error on my other computer with intel gfx. That has absolutely nothing to do with what Liang posted, but please do file a separate bug report for it: https://fedoraproject.org/wiki/How_to_debug_Xorg_problems thanks! again criticizing the reporter for reporting his case. That was what he was Um, where did I criticize anyone? I just told the reporter it wasn't the same bug. from the descriptions I have seen on this thread there is a possibility that it was, although remote. Maybe it is the tone of what you are saying. Tone it down and be more tolerant is by far a more rational approach. People won't report their observation then where will you be. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel-2.6.31.6-134 seems to have a bug on R600 DRM
On 11/24/2009 09:54 AM, Otto Haliburton wrote: from the descriptions I have seen on this thread there is a possibility that it was, although remote. Maybe it is the tone of what you are saying. Tone it down and be more tolerant is by far a more rational approach. People won't report their observation then where will you be. Everybody here is being very tolerant. Telling a user that it isn't the same bug is just being helpful. Rahul -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
RE: Kernel-2.6.31.6-134 seems to have a bug on R600 DRM
That has absolutely nothing to do with what Liang posted, but please do file a separate bug report for it: https://fedoraproject.org/wiki/How_to_debug_Xorg_problems thanks! again criticizing the reporter for reporting his case. That was what he was Um, where did I criticize anyone? I just told the reporter it wasn't the same bug. from the descriptions I have seen on this thread there is a possibility that it was, although remote. Maybe it is the tone of what you are saying. Tone it down and be more tolerant is by far a more rational approach. People won't report their observation then where will you be. Otto, what monitor do you have? Mine is just an ordinary flat panel display and doesn't show the 'tone' of a message. I'd love a display like yours since text is such an awkward medium and I often find myself adding 'tone' while reading emails, only to wonder if I've got the tone right. sincerely ;-] Rodd -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
RE: Kernel failure while writing DVD-RAM
On Sat 2009-11-14, Gilboa Davara wrote: On Thu, 2009-11-12 at 16:10 +, Dave Higton wrote: I'm testing DVD-RAM writing and reading for reliability under Fedoras 10 and 5. While writing some files under F10 this afternoon, there was a kernel failure. Details below: WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x27/0x79() (Not tainted) Hardware name: OptiPlex 755 Modules linked in: udf crc_itu_t fuse i915 drm bridge stp bnep sco l2cap bluetooth sunrpc nf_conntrack_netbios_ns nf_conntrack_ftp ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipv6 cpufreq_ondemand acpi_cpufreq dm_multipath uinput snd_hda_intel snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_hwdep ata_generic i2c_i801 snd ppdev i2c_core iTCO_wdt iTCO_vendor_support parport_pc pata_acpi serio_raw dcdbas soundcore pcspkr parport e1000e e1000 joydev [last unloaded: microcode] Pid: 12876, comm: fillDVD2 Not tainted 2.6.27.37-170.2.104.fc10.i686 #1 [c042ddfb] warn_on_slowpath+0x65/0x8b [c04228dc] ? __enqueue_entity+0xe3/0xeb [c0424346] ? enqueue_entity+0x203/0x20b [c06abe09] ? _spin_lock+0x8/0xb [c0495510] ? inode_sub_bytes+0x69/0x71 [c04afeef] mark_buffer_dirty+0x27/0x79 [f8ea4cb3] udf_bitmap_free_blocks+0xf8/0x12e [udf] [f8ea51ba] udf_free_blocks+0x62/0x8c [udf] [f8eae3f1] extent_trunc+0xe5/0xf0 [udf] [f8eae88a] udf_discard_prealloc+0xce/0x17b [udf] [f8ea5844] udf_release_file+0x18/0x22 [udf] [c04939ad] __fput+0xad/0x13d [c0493a54] fput+0x17/0x19 [c04912e7] filp_close+0x50/0x5a [c0491363] sys_close+0x72/0xb1 [c0404c8a] syscall_call+0x7/0xb === ---[ end trace d4c5a1d53380a8a7 ]--- This is a standard installation from a Fedora 10 DVD, whose image was taken from the web. Other than yup, it's broken, does the above trace mean anything to anyone, and is there anything I can do to make it work reliably or even to diagnose it further? fillDVD2 is my app, written in C, which simply writes sequential files of 1 MB each to the DVD on /dev/sr0. I can post the source if anyone wants to see it. Looking further ahead, the aim was to try to fix writing DVD-RAM under Fedora 5. We know this is broken, and I was hoping to back-port the F10 code to F5. Up to now, we had only observed failures under F5, never F10 - this is the first. The failures were entirely different: F5 would occasionally fail to write beyond 4 GB, and would consistently write DVD-RAMs that showed allocation errors when examined by the Philips udf_test application. F10 has never exhibited either of those failures. F5 has never shown an oops. Now it seems I can no longer rely on the F10 UDF code either. Dave Dave, This doesn't look like an oops. This is a simple WARN_ON (or actually, in this case, warn_slowpath). OK. I've just been Googling for warn_slowpath, but although I've found lots of examples, I don't know what it means. My guess is that it's used as a diagnostic by some code, probably kernel code, so the next challenge is to find where it was called from. Yes? Are you getting a real crash or some kind of failure. More information since my original posting: fillDVD2 is a test app that I wrote as part of an effort to test the ability of Fedora to write DVD-RAM discs. We have experienced numerous failures, but we don't yet understand why. fillDVD2 wasn't testing for errors. An error occurred somewhere, but fillDVD2 carried on trying to write to the DVD-RAM disc. This doesn't work; once DVD-RAM writing has failed, no subsequent attempts will succeed. The disc has to be ejected. I revised fillDVD2 to stop on an error. A subsequent test showed that the first error, at a similar point (when the disc was within a few hundred MB of getting full), was I/O error. Not very meaningful to me. Can you please post: A. Kernel version. uname -a says: 2.6.27.38-170.2.113.fc10.i686 #1 SMP Wed Nov 4 17:55:39 EST 2009 i686 i686 i386 GNULinux B. Serial port output. (Should capture the actual OOPs) I don't have anything connected to the serial port - it never occurred to me to do so. I'll see what I can do. Beyond that, F10 is nearing EOL. I'd suggest you hurry up and file a bug report before it dies. Maybe the Fedora kernel guys will fix in the last F10 update. (I'd also include the fillDVD code in the bug report.) OK. As for back-porting fixes from F10 to F5, I'd consider switching to CentOS/RHEL 5.4 instead, and back porting only the important stuff you really (really) need from F10. We originally wanted to use CentOS but were never able to solve a real-time problem it gave us: we need to service interrupts from our cards every 32 ms. Normally the IRQ is active for no more than 8 us before it's serviced; under CentOS this would often exceed 20 ms and we
Re: Kernel failure while writing DVD-RAM
On Thu, 2009-11-12 at 16:10 +, Dave Higton wrote: I'm testing DVD-RAM writing and reading for reliability under Fedoras 10 and 5. While writing some files under F10 this afternoon, there was a kernel failure. Details below: WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x27/0x79() (Not tainted) Hardware name: OptiPlex 755 Modules linked in: udf crc_itu_t fuse i915 drm bridge stp bnep sco l2cap bluetooth sunrpc nf_conntrack_netbios_ns nf_conntrack_ftp ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipv6 cpufreq_ondemand acpi_cpufreq dm_multipath uinput snd_hda_intel snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_hwdep ata_generic i2c_i801 snd ppdev i2c_core iTCO_wdt iTCO_vendor_support parport_pc pata_acpi serio_raw dcdbas soundcore pcspkr parport e1000e e1000 joydev [last unloaded: microcode] Pid: 12876, comm: fillDVD2 Not tainted 2.6.27.37-170.2.104.fc10.i686 #1 [c042ddfb] warn_on_slowpath+0x65/0x8b [c04228dc] ? __enqueue_entity+0xe3/0xeb [c0424346] ? enqueue_entity+0x203/0x20b [c06abe09] ? _spin_lock+0x8/0xb [c0495510] ? inode_sub_bytes+0x69/0x71 [c04afeef] mark_buffer_dirty+0x27/0x79 [f8ea4cb3] udf_bitmap_free_blocks+0xf8/0x12e [udf] [f8ea51ba] udf_free_blocks+0x62/0x8c [udf] [f8eae3f1] extent_trunc+0xe5/0xf0 [udf] [f8eae88a] udf_discard_prealloc+0xce/0x17b [udf] [f8ea5844] udf_release_file+0x18/0x22 [udf] [c04939ad] __fput+0xad/0x13d [c0493a54] fput+0x17/0x19 [c04912e7] filp_close+0x50/0x5a [c0491363] sys_close+0x72/0xb1 [c0404c8a] syscall_call+0x7/0xb === ---[ end trace d4c5a1d53380a8a7 ]--- This is a standard installation from a Fedora 10 DVD, whose image was taken from the web. Other than yup, it's broken, does the above trace mean anything to anyone, and is there anything I can do to make it work reliably or even to diagnose it further? fillDVD2 is my app, written in C, which simply writes sequential files of 1 MB each to the DVD on /dev/sr0. I can post the source if anyone wants to see it. Looking further ahead, the aim was to try to fix writing DVD-RAM under Fedora 5. We know this is broken, and I was hoping to back-port the F10 code to F5. Up to now, we had only observed failures under F5, never F10 - this is the first. The failures were entirely different: F5 would occasionally fail to write beyond 4 GB, and would consistently write DVD-RAMs that showed allocation errors when examined by the Philips udf_test application. F10 has never exhibited either of those failures. F5 has never shown an oops. Now it seems I can no longer rely on the F10 UDF code either. Dave Dave, This doesn't look like an oops. This is a simple WARN_ON (or actually, in this case, warn_slowpath). Are you getting a real crash or some kind of failure. Can you please post: A. Kernel version. B. Serial port output. (Should capture the actual OOPs) Beyond that, F10 is nearing EOL. I'd suggest you hurry up and file a bug report before it dies. Maybe the Fedora kernel guys will fix in the last F10 update. (I'd also include the fillDVD code in the bug report.) As for back-porting fixes from F10 to F5, I'd consider switching to CentOS/RHEL 5.4 instead, and back porting only the important stuff you really (really) need from F10. P.S. Are you by any chance related to Nice U.K? If so, please say Hello to Russ. - Gilboa -- 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 Change Logs
2009/11/9 Andrew Jamison li...@blogmethat.net Is there an easy way to see the changes between Fedora kernel versions so we can see what has been altered/added when we update a kernel? -- 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, you can check the changelog of the kernel rpm: $ rpm -q --changelog kernel-$(uname -r) (supposing that your current kernel is the latest one) -- 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 Change Logs
Thanks this should work for what i need On Mon, 2009-11-09 at 16:59 +0100, Pikachu_2014 wrote: 2009/11/9 Andrew Jamison li...@blogmethat.net Is there an easy way to see the changes between Fedora kernel versions so we can see what has been altered/added when we update a kernel? -- 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, you can check the changelog of the kernel rpm: $ rpm -q --changelog kernel-$(uname -r) (supposing that your current kernel is the latest one) -- 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 signature.asc Description: This is a digitally signed message part -- 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 installs not showing up in grub.conf
Am 2009-11-06 20:00, schrieb Ahmed Kamal: Seems like I'm hitting https://bugzilla.redhat.com/show_bug.cgi?id=530108 since I'm btrfs root. The updated grubby seems not pushed out yet On Fri, Nov 6, 2009 at 8:40 PM, Bruno Wolff III br...@wolff.to mailto:br...@wolff.to wrote: On Thu, Nov 05, 2009 at 16:08:05 +0200, The firmware warnings are not part of your problem. grubby fatal error: unable to find a suitable template This sounds like none of the entries in grub are close enough to what the package was expecting so it doesn't know how to make one for the current kernel. One way to do this is to move grub.conf out of the way and install a new kernel. You may want to customize the parameters again. We also have the annoying problem of having a menu.lst AND a grub.conf file. Reported here: https://bugzilla.redhat.com/show_bug.cgi?id=533265 -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel using LZMA compression
The executive summary is: Xen does not let a kernel boot itself, because mimicking bare hardware is too tedious (and pointless.) Instead, Xen instantiates an instance of a kernel into the Xen environment. To do this instantiation, Xen does its own decompression, so Xen must know everything about the compression. I know you're right. But that sound stupid to me: The kernel itself has routines built-in for decompression. Why isn't it enough to let Xen use the same routines for decompression as the kernel? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel using LZMA compression
On 11/04/2009 06:18 PM, Ikem Krueger wrote: The executive summary is: Xen does not let a kernel boot itself, because mimicking bare hardware is too tedious (and pointless.) Instead, Xen instantiates an instance of a kernel into the Xen environment. To do this instantiation, Xen does its own decompression, so Xen must know everything about the compression. I know you're right. But that sound stupid to me: The kernel itself has routines built-in for decompression. Why isn't it enough to let Xen use the same routines for decompression as the kernel? I am reading between the lines here (I have never looked at this stuff in Xen) but I would assume it's for the reason given above. The kernel's own decompression routines must run very early on in the boot process - well before the first line of C code runs and while the CPU (on x86) is still running in legacy real addressing mode (right after the handover from the bootloader and relocation of the kernel image). It's emulating this early-boot environment that is tedious and pointless and being able to use the in-kernel decompresser is not sufficient motivation to go down that route. Regards, Bryn. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel using LZMA compression
I am reading between the lines here (I have never looked at this stuff in Xen) but I would assume it's for the reason given above. The kernel's own decompression routines must run very early on in the boot process - well before the first line of C code runs and while the CPU (on x86) is still running in legacy real addressing mode (right after the handover from the bootloader and relocation of the kernel image). Ok. Sounds plausible. How is it to seperate the routines? Can they brought from legacy mode to real mode? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel using LZMA compression
On 11/04/2009 06:37 PM, Ikem Krueger wrote: I am reading between the lines here (I have never looked at this stuff in Xen) but I would assume it's for the reason given above. The kernel's own decompression routines must run very early on in the boot process - well before the first line of C code runs and while the CPU (on x86) is still running in legacy real addressing mode (right after the handover from the bootloader and relocation of the kernel image). Ok. Sounds plausible. How is it to seperate the routines? Can they brought from legacy mode to real mode? Quite tricky I'd guess - it's chicken-and-egg. The code to switch the CPU from real mode to protected mode is in the kernel's startup routines *inside* the compressed image. I don't think anyone is going to want to reorganise things to move that code to the primitive early-boot period - the idea is to do as little as possible in that part of the kernel and leave everything else to later in the boot process when life gets easier. Decompressing the kernel is always going to be done in that part of the startup sequence because that's when it has to happen. Regards, Bryn. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel using LZMA compression
On Sat, Oct 31, 2009 at 2:24 PM, Ikem Krueger ikem.krue...@googlemail.com wrote: As I know, the kernel is compressed with bzip2 or gzip. How about using LZMA instead? Or is that already the case? There is such an option but it is currently disabled due to missing support in xen. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel using LZMA compression
As I know, the kernel is compressed with bzip2 or gzip. How about using LZMA instead? Or is that already the case? There is such an option but it is currently disabled due to missing support in xen. Thanks. But don't understand. What has LZMA todo with Xen? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel using LZMA compression
On Sat, Oct 31, 2009 at 6:03 PM, Ikem Krueger ikem.krue...@googlemail.com wrote: As I know, the kernel is compressed with bzip2 or gzip. How about using LZMA instead? Or is that already the case? There is such an option but it is currently disabled due to missing support in xen. Thanks. But don't understand. What has LZMA todo with Xen? https://bugzilla.redhat.com/show_bug.cgi?id=515831 -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel using LZMA compression
Thanks. But don't understand. What has LZMA todo with Xen? https://bugzilla.redhat.com/show_bug.cgi?id=515831 The executive summary is: Xen does not let a kernel boot itself, because mimicking bare hardware is too tedious (and pointless.) Instead, Xen instantiates an instance of a kernel into the Xen environment. To do this instantiation, Xen does its own decom- pression, so Xen must know everything about the compression. -- -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel Option Classifications
On Thu, 2009-10-22 at 10:22 -0400, Steve Dickson wrote: Does anybody know if so wiki or guidelines out there that defines how kernel option should be classified? Meaning what does it really means to be 'EXPERIMENTAL' or 'DEVELOPER ONLY'. Are there any criteria that has to be met to change them or is simply up to the maintainer's discretion? Mostly up to their discretion. Robert P. J. Day has been doing a lot of upstream cleanup work - maybe ping him about this? Jon. ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: Kernel 2.6.30.5-43.fc11.x86_64 #1 SMP lockups
On Fri, 2009-09-25 at 10:12 +0100, Andrew Gray (Default) wrote: have now had two lockups of Kernel 2.6.30.5-43.fc11.x86_64 others having problems, any ideas what is causing it :- Sep 25 03:19:38 lquad kernel: general protection fault: [#2] SMP Sep 25 03:19:38 lquad kernel: last sysfs file: /sys/devices/system/cpu/cpu2/cpufreq/scaling_cur_freq Sep 25 03:19:38 lquad kernel: CPU 2 No similar problems on my own system, a Quad Core x86_64 system since I installed the latest kernel namely: vmlinuz-2.6.30.5-43.fc11.jon.x86_64 on September 13th. The kernel was modified slightly to allow preemptive scheduling rather than the default voluntary preemption. The system runs the nvidia proprietary drivers as built on the system itself, using nvidia's script. jon -- 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 update to 2.6.30.5-43.fc11.x86_64 issues
Michael Cronenworth wrote: On 09/07/2009 01:04 PM, Jason Turning wrote: I did the update to kernel 2.6.30.5-43.fc11.x86_64 today, noticed there were updates to pulse audio, and when I rebooted wireless didn't work and I heard these loud sound pops, one at boot, one at login, so I just reverted back to the previous kernel. Anyone having similar issues? What wireless chip do you have? We need more info besides it doesn't work. :) Broadcom, and I think I saw the update for that package, so it was just a bit behind the kernel. But from the other reports of popping, I still haven't fiddled with the new kernel as I haven't been using this laptop very much. The first thing I had done was edit grub to always pull the older kernel. -- 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: Kernel update to 2.6.30.5-43.fc11.x86_64 issues
I updated to the same kernel as well. I am not running wireless, but I am getting the loud speaker pops at login. The pops also happen when starting playback in Banshee 1.4.3. It doesn't happen between tracks, just when starting an initial playlist. I also have this sound popping issue in new kernel. Apart from that I found that my audio input from built-in microphone in my Dell Inspiron laptop also does not work in any application in both new 2.6.30.5-43.fc11.x86_64 kernel and the old 2.6.29 kernel. (arecord, gstreamer-properties, skype etc..). But in the 2.6.29 kernels sound popping is not there. Here is my alsa-info profile. http://www.alsa-project.org/db/?f=3b1e182bec5d61aec5af6a8b687d2efa6b167233 -- 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 update to 2.6.30.5-43.fc11.x86_64 issues
I also have this sound popping issue in new kernel. Apart from that I found that my audio input from built-in microphone in my Dell Inspiron laptop also does not work in any application in both new 2.6.30.5-43.fc11.x86_64 kernel and the old 2.6.29 kernel. (arecord, gstreamer-properties, skype etc..). But in the 2.6.29 kernels sound popping is not there. Last few days both kernel alsa and pulseaudio was updated. Now I have popping sound in speakers and audio input from built-in mics also does not work. Reverting to a old 2.6.29 kernel stops popping but internal mic does not work. So now I want to fix this mic input issue first. In Fedora where should I put options for snd-hda-intel. Is it ok if I created a file '/etc/modprobe.d/alsa-base.conf' and put the line options snd-hda-intel model=dell-m4-2 According to my alsa-info profile @ http://www.alsa-project.org/db/?f=3b1e182bec5d61aec5af6a8b687d2efa6b167233 I have a ICH9 audio controller with a Codec called IDT 92HD71B7X. -- 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 update to 2.6.30.5-43.fc11.x86_64 issues
On Mon, Sep 7, 2009 at 11:04 AM, Jason Turning jturn...@sbcglobal.net wrote: I did the update to kernel 2.6.30.5-43.fc11.x86_64 today, noticed there were updates to pulse audio, and when I rebooted wireless didn't work and I heard these loud sound pops, one at boot, one at login, so I just reverted back to the previous kernel. Anyone having similar issues? I updated to the same kernel as well. I am not running wireless, but I am getting the loud speaker pops at login. The pops also happen when starting playback in Banshee 1.4.3. It doesn't happen between tracks, just when starting an initial playlist. -- 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: Kernel update to 2.6.30.5-43.fc11.x86_64 issues
Hello, Try re-install kernel driver, may your wireless driver NOT included in the new kernel, I faced same issue with Broadcome. Best Regards, Waleed Harbi Success is the sum of small efforts, repeated day in and day out. On Mon, Sep 7, 2009 at 9:04 PM, Jason Turning jturn...@sbcglobal.netwrote: I did the update to kernel 2.6.30.5-43.fc11.x86_64 today, noticed there were updates to pulse audio, and when I rebooted wireless didn't work and I heard these loud sound pops, one at boot, one at login, so I just reverted back to the previous kernel. Anyone having similar issues? -- 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 -- 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 update to 2.6.30.5-43.fc11.x86_64 issues
On Mon, Sep 7, 2009 at 8:04 PM, Jason Turningjturn...@sbcglobal.net wrote: I did the update to kernel 2.6.30.5-43.fc11.x86_64 today, noticed there were updates to pulse audio, and when I rebooted wireless didn't work and I heard these loud sound pops, one at boot, one at login, so I just reverted back to the previous kernel. Anyone having similar issues? In my Dell Inspiron 1545 laptop With this new kernel 2.6.30.5-43.fc11.x86_64 I also have popping sound from speakers during boot and randomly after logged in. When I boot from older 2.6.29 kernel everything works and pulseaudio skype 2.1 problem is also solved. My alsa-info profile (taken from older 2.6.29 kernel since I don't have new kmod-wl for 2.6.30 kernel) is given here http://www.alsa-project.org/db/?f=b67f3d9399b1777256be4d563e1c00a1d57a7233 -- Prasan http://prasan.microsolutions.info http://linux.wellassa.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 update to 2.6.30.5-43.fc11.x86_64 issues
On 09/07/2009 02:04 PM, Jason Turning wrote: I did the update to kernel 2.6.30.5-43.fc11.x86_64 today, noticed there were updates to pulse audio, and when I rebooted wireless didn't work and I heard these loud sound pops, one at boot, one at login, so I just reverted back to the previous kernel. Anyone having similar issues? Booted for me, no pops of any kind from the speakers, wireless works for me (iwl3945). Suspend/Hibernate is still broken for me (its been that way for all of F11), but I haven't tracked that down yet S/H worked fine for me under F9. -- 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 update to 2.6.30.5-43.fc11.x86_64 issues
On 09/07/2009 01:04 PM, Jason Turning wrote: I did the update to kernel 2.6.30.5-43.fc11.x86_64 today, noticed there were updates to pulse audio, and when I rebooted wireless didn't work and I heard these loud sound pops, one at boot, one at login, so I just reverted back to the previous kernel. Anyone having similar issues? What wireless chip do you have? We need more info besides it doesn't 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: Kernel update to 2.6.30.5-43.fc11.x86_64 issues
I'm using the same kernel on: 0c:00.0 Network controller: Intel Corporation PRO/Wireless 5300 AGN [Shiloh] Network Connection Subsystem: Intel Corporation Device 1121 Flags: bus master, fast devsel, latency 0, IRQ 5 Memory at f1ffe000 (64-bit, non-prefetchable) Capabilities: access denied Kernel driver in use: iwlagn Kernel modules: iwlagn which is wireless, and I have no problem whatsoever. By the way, the above is the output of `lspci -vb` in a terminal window. As to sound, 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) Subsystem: Dell Device 0233 Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at f6fdc000 (64-bit, non-prefetchable) Capabilities: access denied Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel that gives the highly specific information needed. Being deaf, I don't actually know if sound works on my computer, nor do I care. Bob On 09/07/2009 05:00 PM, Michael Cronenworth wrote: On 09/07/2009 01:04 PM, Jason Turning wrote: I did the update to kernel 2.6.30.5-43.fc11.x86_64 today, noticed there were updates to pulse audio, and when I rebooted wireless didn't work and I heard these loud sound pops, one at boot, one at login, so I just reverted back to the previous kernel. Anyone having similar issues? What wireless chip do you have? We need more info besides it doesn't 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: Kernel update to 2.6.30.5-43.fc11.x86_64 issues
On 09/07/2009 02:04 PM, Jason Turning wrote: I did the update to kernel 2.6.30.5-43.fc11.x86_64 today, noticed there were updates to pulse audio, and when I rebooted wireless didn't work and I heard these loud sound pops, one at boot, one at login, so I just reverted back to the previous kernel. Anyone having similar issues? Pulse audio no longer works on this kernel for me. I reverted to 2.6.29.6-217.2.16.fc11.x86_64. I have not had a chance to really research the problem yet. Will file a bug report if necessary during the week if time permits. -- Jerry Feldman g...@blu.org Boston Linux and Unix PGP key id: 537C5846 PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607 4319 537C 5846 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 update to 2.6.30.5-43.fc11.x86_64 issues
Hi; On Mon, 2009-09-07 at 11:04 -0700, Jason Turning wrote: I did the update to kernel 2.6.30.5-43.fc11.x86_64 today, noticed there were updates to pulse audio, and when I rebooted wireless didn't work and I heard these loud sound pops, one at boot, one at login, so I just reverted back to the previous kernel. Anyone having similar issues? Just for the record, I also did the update to kernel 2.6.30.5-43.fc11.x86_64 today. I noticed that my weird sounds on booting have now gone away!?!. ALSA sound and RhythmBox are still not working. -- Regards Bill Fedora 11, Gnome 2.26.3 Evo.2.26.3, Emacs 23.1.1 -- 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 217.2.8 won't boot.
Markus Kesaromous wrote: From: linuxguy...@gmail.com To: fedora-list@redhat.com Date: Mon, 24 Aug 2009 11:09:19 -0600 Subject: kernel 217.2.8 won't boot. Kernel 2.6.29.6-217.2.3.fc11.i586 works fine on my laptop, but 217.2.8 won't boot at all. It seems to run through everything just fine and then the video starts blinking like crazy in text mode, like it can't start the nvidia driver. After that I get a black screen with a blinking cursor. Kernel 217.2.3 is working OK for me. I can live without 217.2.8, except that I am worried that the next kernel update will delete it and I might be left with zero working kernels. Any idea on what I could do to get 217.2.8 running ? Thanks $ uname -a Linux localhost.localdomain 2.6.29.6-217.2.3.fc11.i586 #1 SMP Wed Jul 29 15:46:46 EDT 2009 i686 i686 i386 GNU/Linux $ yum list kernel Loaded plugins: dellsysidplugin2, downloadonly, kmdl, priorities, refresh-packagekit 1 packages excluded due to repository priority protections Installed Packages kernel.i586 2.6.29.6-213.fc11 @updates kernel.i586 2.6.29.6-217.2.3.fc11 @updates kernel.i586 2.6.29.6-217.2.8.fc11 @updates $ yum list \*nvidia* Loaded plugins: dellsysidplugin2, downloadonly, kmdl, priorities, refresh-packagekit 1 packages excluded due to repository priority protections Installed Packages kmod-nvidia.i586 185.18.31-1.fc11 @rpmfusion-nonfree-updates kmod-nvidia-2.6.29.6-213.fc11.i586.i586 185.18.29-1.fc11 @rpmfusion-nonfree-updates kmod-nvidia-2.6.29.6-217.2.3.fc11.i586.i586 185.18.31-1.fc11 @rpmfusion-nonfree-updates kmod-nvidia-2.6.29.6-217.2.8.fc11.i586.i586 185.18.14-1.fc11.6 @rpmfusion-nonfree-updates xorg-x11-drv-nvidia.i586 185.18.31-1.fc11 @rpmfusion-nonfree-updates xorg-x11-drv-nvidia-libs.i586 185.18.31-1.fc11 @rpmfusion-nonfree-updates Seems to me fedora kernel is screwing up more things than just video drivers which are supplied by xorg, but some of these drivers do not work on the fedora released kernel. I am currently running FC11 2.6.29.6-217.2.8.fc11.i586 and my radeon driver from xorg seems to eork fine. However, I wanted to see if I could build and install latest 2.6.31-rc7 from kernel.org. Well, kernel configured and built and installed and booted just fine, but no gnome desktop because the radeon driver wont work on this kernel. Ditto with kernel 2.6.30.5 I think the answer is from kernel.org rather than from rawhide in this case. There were many changes in video with the 6.30 and 6.31 kernels, and I tried the rawhide one to fix my Intel video (did). But other things may have to change as well, so using the rawhide kernel is sometimes more successful that a raw kernel.org, particularly if you have custom modules tainting your kernel. You might try doing that. -- Bill Davidsen david...@tmr.com 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: kernel 217.2.8 won't boot.
Date: Tue, 25 Aug 2009 13:56:49 -0400 From: david...@tmr.com To: fedora-list@redhat.com Subject: Re: kernel 217.2.8 won't boot. Markus Kesaromous wrote: From: linuxguy...@gmail.com To: fedora-list@redhat.com Date: Mon, 24 Aug 2009 11:09:19 -0600 Subject: kernel 217.2.8 won't boot. Kernel 2.6.29.6-217.2.3.fc11.i586 works fine on my laptop, but 217.2.8 won't boot at all. It seems to run through everything just fine and then the video starts blinking like crazy in text mode, like it can't start the nvidia driver. After that I get a black screen with a blinking cursor. Kernel 217.2.3 is working OK for me. I can live without 217.2.8, except that I am worried that the next kernel update will delete it and I might be left with zero working kernels. Any idea on what I could do to get 217.2.8 running ? Thanks $ uname -a Linux localhost.localdomain 2.6.29.6-217.2.3.fc11.i586 #1 SMP Wed Jul 29 15:46:46 EDT 2009 i686 i686 i386 GNU/Linux $ yum list kernel Loaded plugins: dellsysidplugin2, downloadonly, kmdl, priorities, refresh-packagekit 1 packages excluded due to repository priority protections Installed Packages kernel.i586 2.6.29.6-213.fc11 @updates kernel.i586 2.6.29.6-217.2.3.fc11 @updates kernel.i586 2.6.29.6-217.2.8.fc11 @updates $ yum list \*nvidia* Loaded plugins: dellsysidplugin2, downloadonly, kmdl, priorities, refresh-packagekit 1 packages excluded due to repository priority protections Installed Packages kmod-nvidia.i586 185.18.31-1.fc11 @rpmfusion-nonfree-updates kmod-nvidia-2.6.29.6-213.fc11.i586.i586 185.18.29-1.fc11 @rpmfusion-nonfree-updates kmod-nvidia-2.6.29.6-217.2.3.fc11.i586.i586 185.18.31-1.fc11 @rpmfusion-nonfree-updates kmod-nvidia-2.6.29.6-217.2.8.fc11.i586.i586 185.18.14-1.fc11.6 @rpmfusion-nonfree-updates xorg-x11-drv-nvidia.i586 185.18.31-1.fc11 @rpmfusion-nonfree-updates xorg-x11-drv-nvidia-libs.i586 185.18.31-1.fc11 @rpmfusion-nonfree-updates Seems to me fedora kernel is screwing up more things than just video drivers which are supplied by xorg, but some of these drivers do not work on the fedora released kernel. I am currently running FC11 2.6.29.6-217.2.8.fc11.i586 and my radeon driver from xorg seems to eork fine. However, I wanted to see if I could build and install latest 2.6.31-rc7 from kernel.org. Well, kernel configured and built and installed and booted just fine, but no gnome desktop because the radeon driver wont work on this kernel. Ditto with kernel 2.6.30.5 I think the answer is from kernel.org rather than from rawhide in this case. There were many changes in video with the 6.30 and 6.31 kernels, and I tried the rawhide one to fix my Intel video (did). But other things may have to change as well, so using the rawhide kernel is sometimes more successful that a raw kernel.org, particularly if you have custom modules tainting your kernel. You might try doing that. -- Bill Davidsen We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot I tried kernel-2.6.30.4-25.fc11.src.rpm and kernel-2.6.31-0.167.rc6.git6.fc12.src.rpm with the same result. No Video! _ With Windows Live, you can organize, edit, and share your photos. http://www.windowslive.com/Desktop/PhotoGallery -- 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 217.2.8 won't boot.
On Mon, 2009-08-24 at 11:09 -0600, Linuxguy123 wrote: Kernel 217.2.3 is working OK for me. I can live without 217.2.8, except that I am worried that the next kernel update will delete it and I might be left with zero working kernels. Change the configuration in yum.conf to keep more than two kernels. Two's not enough for exactly the reason that you're concerned with. e.g. installonly_limit=6 I left mine high after seeing a rapid release of several kernels, yonks ago. I wouldn't recommend more than six, it gets slower for yum/rpm to sort itself out when you want to update/install things, the more you have installed. -- [...@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: kernel 217.2.8 won't boot.
On Tue, 2009-08-25 at 03:35 +0930, Tim wrote: Change the configuration in yum.conf to keep more than two kernels. Two's not enough for exactly the reason that you're concerned with. e.g. installonly_limit=6 Thanks for the tip. I made this change. LG -- 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.29 for F10
On Wed, 2009-08-19 at 14:16 +1000, Rodd Clarkson wrote: Dave, Is this an offer to try and help me get the f12 kernel to boot on my system so that I can test it for you? ;-] https://bugzilla.redhat.com/show_bug.cgi?id=513528 Rodd I'd just like to thank Kyle McMartin for giving me a little help with this (maybe with a little prompting from Dave???) I can now boot rawhide so I can now help with testing. thanks Rodd -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel 2.6.29 for F10
This would be ok if you never pushed it to updates-testing But if you do that it's logical for test-users that they can start testing and not getting 2.6.27 after that - Push it to updatestesting is like go on and after that step there should be no package-conflicts if they were THANK YOU for 2.6.29.6-97 today to help to solve my problems which are nearly killing me because i have no time and energy for downgrades 4 days before my healthy issues (medical operation) especially after working the last weeks day and night nearly to burn-out with other things which had to be done before On Tue, Aug 18, 2009 at 10:13:10AM -0500, Joe Nall wrote: One of the reasons we haven't pushed them as proper updates is that getting the regressions fixed is pretty time consuming, and the limited X/KMS manpower we have is better focused on making the F12 stuff work right, and getting it upstream. signature.asc Description: OpenPGP digital signature -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel 2.6.29 for F10
Reindl Harald wrote: Hi Is there a reason that since longer time 2.6.29-Kernels for Fedora 10 landing in Updates-testing followed with 2.6.27-Builds in the meantime? On machines with kmods this is a real problem because yum detetects the kmod for 2.6.27-Build and wants to install the 2.6.27 kernel which conflicts with the installed one I use the 2.6.29 since months in the meantime, F11 has it since the release and i do not realize why F10 does not get him I've been personally using 2.6.29.4-75 successfully for a while (uptime currently is 32 days), so I join you in asking why there are no recent kernels for f10. On this route, why no 2.6.30? There is a driver I need which is included in = 2.6.30. These days upstream 2.6.31 is almost released... BTW -- Roberto Ragusamail at robertoragusa.it -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel 2.6.29 for F10
On Aug 18, 2009, at 5:16 AM, Reindl Harald wrote: Hi Is there a reason that since longer time 2.6.29-Kernels for Fedora 10 landing in Updates-testing followed with 2.6.27-Builds in the meantime? On machines with kmods this is a real problem because yum detetects the kmod for 2.6.27-Build and wants to install the 2.6.27 kernel which conflicts with the installed one I use the 2.6.29 since months in the meantime, F11 has it since the release and i do not realize why F10 does not get him I tried to ask this on the fedora kernel list and the moderator never approved the message. I too would like to see F10 move up to 2.6.29+ prior to end-of-life. joe -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel 2.6.29 for F10
On Tue, Aug 18, 2009 at 10:13:10AM -0500, Joe Nall wrote: On Aug 18, 2009, at 5:16 AM, Reindl Harald wrote: Hi Is there a reason that since longer time 2.6.29-Kernels for Fedora 10 landing in Updates-testing followed with 2.6.27-Builds in the meantime? On machines with kmods this is a real problem because yum detetects the kmod for 2.6.27-Build and wants to install the 2.6.27 kernel which conflicts with the installed one I use the 2.6.29 since months in the meantime, F11 has it since the release and i do not realize why F10 does not get him I tried to ask this on the fedora kernel list and the moderator never approved the message. Odd, I don't recall seeing it, and there's no non-spam messages in the queue right now. I too would like to see F10 move up to 2.6.29+ prior to end-of-life. In days of old, we were able to get rebases out pretty quickly after their upstream release. These days, we're hindered by the kernel modesetting stuff we're carrying. It's closely tied to the userspace X drivers, and isn't easy to retrofit to a different kernel. One of the reasons we haven't pushed them as proper updates is that getting the regressions fixed is pretty time consuming, and the limited X/KMS manpower we have is better focused on making the F12 stuff work right, and getting it upstream. I really can't wait for the day that it all gets upstream, and we can get back to the old routine of rebasing. Until then, we're kinda stuck. Dave -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel 2.6.29 for F10
I too would like to see F10 move up to 2.6.29+ prior to end-of-life. In days of old, we were able to get rebases out pretty quickly after their upstream release. These days, we're hindered by the kernel modesetting stuff we're carrying. It's closely tied to the userspace X drivers, and isn't easy to retrofit to a different kernel. One of the reasons we haven't pushed them as proper updates is that getting the regressions fixed is pretty time consuming, and the limited X/KMS manpower we have is better focused on making the F12 stuff work right, and getting it upstream. Dave, Is this an offer to try and help me get the f12 kernel to boot on my system so that I can test it for you? ;-] https://bugzilla.redhat.com/show_bug.cgi?id=513528 Rodd -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: kernel 2.6.29.6-217.2.3.fc11 compiled from source will not boot
On Sunday 09 August 2009 11:16:12 pm Markus Kesaromous wrote: There is something seriously wrong with this kernel release. Again -- the list you want is fedora-kernel-list, NOT fedora-devel-list. Regards, -- Conrad Meyer ceme...@u.washington.edu -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: kernel 2.6.29.6-217.2.3.fc11 compile d from source will not boot
2009/8/10 Markus Kesaromous remotes...@live.com: Dear list, There is something seriously wrong with this kernel release. It compiles - but will not boot all the way. It hangs somewhere. I even tried to boot into single user mode. I never get to the shell prompt when booting in single user mode, nor to the gnome login banner when letting it boot in multiuser mode. After some 30-45 minutes I Ctrl-Alt_Del and the kernel pops the message Stopping all md devices .. and the pc reboots. I did not have this problem with these kernels 2.6.29.6-213.fc11 2.6.29.5-191.fc11 Are there others who have tried to build 2.6.29.6-217.2.3.fc11 from source rpm and configured the kernel in any way before building? Did you see any errors when running make modules_install as I did? Did the resulting kernel boot up all the way? If you need more info, please let me know. The main piece of information you appear to have missed off is the modifications you have made in your build. I would suggest the following for further reading: http://fedoraproject.org/wiki/Docs/CustomKernel http://fedoraproject.org/wiki/KernelCommonProblems Regards -- Christopher Brown ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
RE: kernel 2.6.29.6-217.2.3.fc11 compiled from source will not boot
On Tue, 11 Aug 2009 00:41:52AM, Christopher Brown wrote: Date: Tue, 11 Aug 2009 00:41:52 +0100 From: snecklif...@gmail.com To: remotes...@live.com CC: fedora-kernel-list@redhat.com Subject: Re: kernel 2.6.29.6-217.2.3.fc11 compiled from source will not boot 2009/8/10 Markus Kesaromous : Dear list, There is something seriously wrong with this kernel release. It compiles - but will not boot all the way. It hangs somewhere. I even tried to boot into single user mode. I never get to the shell prompt when booting in single user mode, nor to the gnome login banner when letting it boot in multiuser mode. After some 30-45 minutes I Ctrl-Alt_Del and the kernel pops the message Stopping all md devices .. and the pc reboots. I did not have this problem with these kernels 2.6.29.6-213.fc11 2.6.29.5-191.fc11 Are there others who have tried to build 2.6.29.6-217.2.3.fc11 from source rpm and configured the kernel in any way before building? Did you see any errors when running make modules_install as I did? Did the resulting kernel boot up all the way? If you need more info, please let me know. The main piece of information you appear to have missed off is the modifications you have made in your build. I would suggest the following for further reading: http://fedoraproject.org/wiki/Docs/CustomKernel http://fedoraproject.org/wiki/KernelCommonProblems Regards -- Christopher Brown Thank you Christopher. The steps to build the kernel at URL http://fedoraproject.org/wiki/Docs/CustomKernel were exactly what I needed. I was not aware of this document before. The only thing extra I had to do was to untar linux-2.6.29.tar.bz2 and fix drivers/staging/rt2860/config.mk, and then re-tar. Guess I should have created a patch, and should have added that patch to the spec file. But, since this is only one-off, I did not see the need for it. I am sure there will be yet another kernel update for whic I will have to repeat this whole process. What a pain in the neck! If I had known that the Atheros 9K series of mini-pci cards were supported natively, I would not have bought the Ralink 2860 card. Thanx again for your help. Cheers, Markus _ Get back to school stuff for them and cashback for you. http://www.bing.com/cashback?form=MSHYCBpubl=WLHMTAGcrea=TEXT_MSHYCB_BackToSchool_Cashback_BTSCashback_1x1 ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: Kernel built from source stuck during boot
Markus Kesaromous wrote: Dear list, I installed kernel 2.6.29.6-213 from source rpm. I did not build it via rpmbuild. Rather, I first ran rpmbuild -v -bp kernel.spec then I cd'ed to BUILD/kernel-2.6.29/linux-2.6.29.i586 I configured it (make xconfig) and built it - make all. Build went witout a hitch. Ditto with Install and modules_install. At bootup, it quickly scrolls through some output of probed devices and seems to stop there. No gui. No login prompt. The KB driver does respond to keyboard key strokes. But other than that, nothing. My machine is a UP, AMD Athlon64 (but I compile only for 32 bit). In xconfig, I disabled all SMP stuff. I set the frequency governor to Performance, among other things (such as enabling rt2860 driver in the staging area). Would someone on this list be able to have a look at the .config file and tell me what is missing or mis-configured? Not sure if I should attach the config file here, or send it as an attachment to someone who is willing to have look and get back to me. Please advise. Cheers, MK _ Get free photo software from Windows Live http://www.windowslive.com/online/photos?ocid=PID23393::T:WLMTAGL:ON:WL:en-US:SI_PH_software:082009 You may attach it here. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
RE: Kernel built from source stuck during boot
Date: Sun, 2 Aug 2009 14:22:38 +0300 From: scha...@gmail.com To: fedora-devel-list@redhat.com Subject: Re: Kernel built from source stuck during boot Markus Kesaromous wrote: Dear list, I installed kernel 2.6.29.6-213 from source rpm. I did not build it via rpmbuild. Rather, I first ran rpmbuild -v -bp kernel.spec then I cd'ed to BUILD/kernel-2.6.29/linux-2.6.29.i586 I configured it (make xconfig) and built it - make all. Build went witout a hitch. Ditto with Install and modules_install. At bootup, it quickly scrolls through some output of probed devices and seems to stop there. No gui. No login prompt. The KB driver does respond to keyboard key strokes. But other than that, nothing. My machine is a UP, AMD Athlon64 (but I compile only for 32 bit). In xconfig, I disabled all SMP stuff. I set the frequency governor to Performance, among other things (such as enabling rt2860 driver in the staging area). Would someone on this list be able to have a look at the .config file and tell me what is missing or mis-configured? Not sure if I should attach the config file here, or send it as an attachment to someone who is willing to have look and get back to me. Please advise. Cheers, MK _ Get free photo software from Windows Live http://www.windowslive.com/online/photos?ocid=PID23393::T:WLMTAGL:ON:WL:en-US:SI_PH_software:082009 You may attach it here. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list .config.bz2 attached. Thanx!! MK _ Get back to school stuff for them and cashback for you. http://www.bing.com/cashback?form=MSHYCBpubl=WLHMTAGcrea=TEXT_MSHYCB_BackToSchool_Cashback_BTSCashback_1x1 .config.bz2 Description: BZip2 compressed data -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
RE: Kernel built from source stuck during boot
Date: Sun, 2 Aug 2009 18:15:49 +0300 From: scha...@gmail.com To: fedora-devel-list@redhat.com Subject: Re: Kernel built from source stuck during boot Markus Kesaromous wrote: Date: Sun, 2 Aug 2009 14:22:38 +0300 From: scha...@gmail.com To: fedora-devel-list@redhat.com Subject: Re: Kernel built from source stuck during boot Markus Kesaromous wrote: Dear list, I installed kernel 2.6.29.6-213 from source rpm. I did not build it via rpmbuild. Rather, I first ran rpmbuild -v -bp kernel.spec then I cd'ed to BUILD/kernel-2.6.29/linux-2.6.29.i586 I configured it (make xconfig) and built it - make all. Build went witout a hitch. Ditto with Install and modules_install. At bootup, it quickly scrolls through some output of probed devices and seems to stop there. No gui. No login prompt. The KB driver does respond to keyboard key strokes. But other than that, nothing. My machine is a UP, AMD Athlon64 (but I compile only for 32 bit). In xconfig, I disabled all SMP stuff. I set the frequency governor to Performance, among other things (such as enabling rt2860 driver in the staging area). Would someone on this list be able to have a look at the .config file and tell me what is missing or mis-configured? Not sure if I should attach the config file here, or send it as an attachment to someone who is willing to have look and get back to me. Please advise. Cheers, MK _ Get free photo software from Windows Live http://www.windowslive.com/online/photos?ocid=PID23393::T:WLMTAGL:ON:WL:en-US:SI_PH_software:082009 You may attach it here. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list .config.bz2 attached. Thanx!! MK _ Get back to school stuff for them and cashback for you. http://www.bing.com/cashback?form=MSHYCBpubl=WLHMTAGcrea=TEXT_MSHYCB_BackToSchool_Cashback_BTSCashback_1x1 It may help if you can specify exactly at what point does your booting process stop. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list It stops after it displays the USB keyboard and mouse devices (per console output). The keyboard is responsive when it hangs. The driver echoes whatever I type. But no other effects are evident from typing. For example ^C simply echoes ^C. After waiting about 30 minutes, I had to Ctrl-Alt-Del to reboot. Thank you for your help. MK _ Windows Live™: Keep your life in sync. http://windowslive.com/explore?ocid=PID23384::T:WLMTAGL:ON:WL:en-US:NF_BR_sync:082009 -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Kernel built from source stuck during boot
Markus Kesaromous wrote: Date: Sun, 2 Aug 2009 18:15:49 +0300 From: scha...@gmail.com To: fedora-devel-list@redhat.com Subject: Re: Kernel built from source stuck during boot Markus Kesaromous wrote: Date: Sun, 2 Aug 2009 14:22:38 +0300 From: scha...@gmail.com To: fedora-devel-list@redhat.com Subject: Re: Kernel built from source stuck during boot Markus Kesaromous wrote: Dear list, I installed kernel 2.6.29.6-213 from source rpm. I did not build it via rpmbuild. Rather, I first ran rpmbuild -v -bp kernel.spec then I cd'ed to BUILD/kernel-2.6.29/linux-2.6.29.i586 I configured it (make xconfig) and built it - make all. Build went witout a hitch. Ditto with Install and modules_install. At bootup, it quickly scrolls through some output of probed devices and seems to stop there. No gui. No login prompt. The KB driver does respond to keyboard key strokes. But other than that, nothing. My machine is a UP, AMD Athlon64 (but I compile only for 32 bit). In xconfig, I disabled all SMP stuff. I set the frequency governor to Performance, among other things (such as enabling rt2860 driver in the staging area). Would someone on this list be able to have a look at the .config file and tell me what is missing or mis-configured? Not sure if I should attach the config file here, or send it as an attachment to someone who is willing to have look and get back to me. Please advise. Cheers, MK _ Get free photo software from Windows Live http://www.windowslive.com/online/photos?ocid=PID23393::T:WLMTAGL:ON:WL:en-US:SI_PH_software:082009 You may attach it here. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list .config.bz2 attached. Thanx!! MK _ Get back to school stuff for them and cashback for you. http://www.bing.com/cashback?form=MSHYCBpubl=WLHMTAGcrea=TEXT_MSHYCB_BackToSchool_Cashback_BTSCashback_1x1 It may help if you can specify exactly at what point does your booting process stop. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list It stops after it displays the USB keyboard and mouse devices (per console output). The keyboard is responsive when it hangs. The driver echoes whatever I type. But no other effects are evident from typing. For example ^C simply echoes ^C. After waiting about 30 minutes, I had to Ctrl-Alt-Del to reboot. Thank you for your help. MK _ Windows Live™: Keep your life in sync. http://windowslive.com/explore?ocid=PID23384::T:WLMTAGL:ON:WL:en-US:NF_BR_sync:082009 Try unplugging them (the usb keyboard and mouse) by using ps/2 peripherals and see if that occurs again and where, please. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
RE: Kernel built from source stuck during boot
Date: Sun, 2 Aug 2009 21:46:35 +0300 From: scha...@gmail.com To: fedora-devel-list@redhat.com Subject: Re: Kernel built from source stuck during boot Markus Kesaromous wrote: Date: Sun, 2 Aug 2009 18:15:49 +0300 From: scha...@gmail.com To: fedora-devel-list@redhat.com Subject: Re: Kernel built from source stuck during boot Markus Kesaromous wrote: Date: Sun, 2 Aug 2009 14:22:38 +0300 From: scha...@gmail.com To: fedora-devel-list@redhat.com Subject: Re: Kernel built from source stuck during boot Markus Kesaromous wrote: Dear list, I installed kernel 2.6.29.6-213 from source rpm. I did not build it via rpmbuild. Rather, I first ran rpmbuild -v -bp kernel.spec then I cd'ed to BUILD/kernel-2.6.29/linux-2.6.29.i586 I configured it (make xconfig) and built it - make all. Build went witout a hitch. Ditto with Install and modules_install. At bootup, it quickly scrolls through some output of probed devices and seems to stop there. No gui. No login prompt. The KB driver does respond to keyboard key strokes. But other than that, nothing. My machine is a UP, AMD Athlon64 (but I compile only for 32 bit). In xconfig, I disabled all SMP stuff. I set the frequency governor to Performance, among other things (such as enabling rt2860 driver in the staging area). Would someone on this list be able to have a look at the .config file and tell me what is missing or mis-configured? Not sure if I should attach the config file here, or send it as an attachment to someone who is willing to have look and get back to me. Please advise. Cheers, MK _ Get free photo software from Windows Live http://www.windowslive.com/online/photos?ocid=PID23393::T:WLMTAGL:ON:WL:en-US:SI_PH_software:082009 You may attach it here. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list .config.bz2 attached. Thanx!! MK _ Get back to school stuff for them and cashback for you. http://www.bing.com/cashback?form=MSHYCBpubl=WLHMTAGcrea=TEXT_MSHYCB_BackToSchool_Cashback_BTSCashback_1x1 It may help if you can specify exactly at what point does your booting process stop. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list It stops after it displays the USB keyboard and mouse devices (per console output). The keyboard is responsive when it hangs. The driver echoes whatever I type. But no other effects are evident from typing. For example ^C simply echoes ^C. After waiting about 30 minutes, I had to Ctrl-Alt-Del to reboot. Thank you for your help. MK _ Windows Live™: Keep your life in sync. http://windowslive.com/explore?ocid=PID23384::T:WLMTAGL:ON:WL:en-US:NF_BR_sync:082009 Try unplugging them (the usb keyboard and mouse) by using ps/2 peripherals and see if that occurs again and where, please. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list I have recompiled and re-installed the kernel with only one change: I unchecked the config option for Opteron/Athlon64 and checked the config option which sets i586 cpu type. I saved and quit xconfig. Diffing the new .config file against the previous one: $ diff .config.sav .config 4c4 # Sun Aug 2 07:56:07 2009 --- # Sun Aug 2 12:47:01 2009 209c209 # CONFIG_M586 is not set --- CONFIG_M586=y 219c219 CONFIG_MK8=y --- # CONFIG_MK8 is not set 236a237,238 # CONFIG_X86_PPRO_FENCE is not set CONFIG_X86_F00F_BUG=y 240a243 CONFIG_X86_ALIGNMENT_16=y 242,244d244 CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_TSC=y CONFIG_X86_CMOV=y 246d245 CONFIG_X86_DEBUGCTLMSR=y 253d251 # CONFIG_X86_DS is not set I recompiled , installed and rebooted. All went well. I am sorry that i could not re-boot the non functioning kernel because I had to get something working. So at this time I am not so keen on rebuilding the kernel with the older .config file because it takes so darned long to compile the kernel. My understanding now is that when compiling for x86 32 bit type of architecture, AND your cpu is AMD 64, do not choose the AMD 64 type of cpu during config. Perhaps I am wrong - but I had to do something to get up and running. As soon as I clear up some important work out of the way, I WILL retry and build using the old config, and reboot with the USB devices unplpugged, and get back to you. Just gimme a couple of days please. Best regards, MK _ Express your personality in color! Preview and select themes
Re: kernel 2.6.30.3 - F11 or FC11 in koji terms
On 26/07/09 00:06, Mail Lists wrote: I dont see 2.6.30 builds on koji - can we please get a current stable kernel ( 2.6.30.3 ) so it can get into updates testing ? Thanks. I just use the rawhide kernels in F11 kernel-2.6.31-0.86.rc3.git5.fc12.x86_64 As they usually update faster. And you can get stable kernels. -- 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.30 on Fedora 10
Michael Eager eager at eagercon.com writes: kernel-2.6.30. This kernel is available on F11 and F12. I'm running F11. Where can I find this kernel? -- 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.30 on Fedora 10
On Fri, Jul 10, 2009 at 14:24:46 +, davide lists4dav...@gmail.com wrote: Michael Eager eager at eagercon.com writes: kernel-2.6.30. This kernel is available on F11 and F12. I'm running F11. Where can I find this kernel? No 2.6.30 kernels got pushed to bodhi. In koji I haven't see any for dist-f11 or dist-f10. Rawhide is using 2.6.31 kernels. Fixes are still getting back ported to 2.6.29. For example kernel-2.6.29.6-213.fc11 is pending for updates-testing in F11. I think that 2.6.31 is far enough away, that 2.6.30 will probably make it into F10 and F11 at some 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 Loading Sequence
On Monday 06 July 2009 11:57:47 Ahmad Al-Yaman wrote: Hi all, I came across a problem when trying to compile a custom kernel for F11: both the stock kernel and my custom kernel have i915 modesetting enabled by default. In the stock kernel the loading screen starts up immediately when the kernel starts loading, but using the custom kernel, some text is displayed before the loading screen starts up (the kernel finishes loading without problems). I'm trying to figure out the reason for this and if there's a way to fix it so that the user doesn't see this text. Could the reason be the order in which different parts of the kernel are loaded? If yes, how can I control which parts load first? Is your 'custom kernel' an F11 kernel + your patches, or starting from an upstream tarball + your patches? (In which case, its lacking all the patches Fedora has added, and therein probably lies your answer to why things are behaving differently). -- Jarod Wilson ja...@redhat.com ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: Kernel 2.6.30
If kernel.org releases 2.6.30.1, Are there any delta *.tar.gz's that one can download instead of downloading the full kernel source again to update to 2.6.30.1? I have been yearning to ask this question, but never had the courage or the determination to do so. I generally follow Fedora kernels, but sometimes I get eager to run the latest and greatest. I run rawhide too, but they are at 2.6.30-6.fc12. Someone told me that there were patches that one could download and recompile to get the latest version, but they don't tell me how and there does not seem to exist documentation as to how to do it. All of this in case Fedora stays a little bit behind, they are doing the right thing though testing and making sure that the kernels work :), and that the changes upstream do not affect the endusers in a bad way. Regards, Antonio How to patch the Linux kernel Download the latest patch file for the kernel you're running - You'll see it on the kernel.org website. Put the patch file in the directory with the original, unpatched kernel source. Run make mrproper. Run bunzip to uncompress the patch file. Run patch -P1 patch-file-name Now your kernel is patched to the latest version. Do your kernel build. http://www.kernel.org/pub/linux/kernel/v2.6/patch-2.6.30.1.bz2 Patch is out for 2.6.30.1, how exactly do I do it. I run patch -P1 patch-2.6.30.1.bz2 in /linux-2.6.30 directory where the 2.6.30 source was? Do I extract the patch? This is where I need more guidance as I have not done it. Usually I just get the entire thing 2.6.30.1.tar.bz2 but now I don't have access to high speed connection and I just want to see if I can do it. Thanks in advance, Antonio -- 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.30
http://www.kernel.org/pub/linux/kernel/v2.6/patch-2.6.30.1.bz2 Patch is out for 2.6.30.1, how exactly do I do it. I run patch -P1 patch-2.6.30.1.bz2 in /linux-2.6.30 directory where the 2.6.30 source was? Do I extract the patch? This is where I need more guidance as I have not done it. Usually I just get the entire thing 2.6.30.1.tar.bz2 but now I don't have access to high speed connection and I just want to see if I can do it. Thanks in advance, Antonio Ok, I am applying the steps as I wrote this, and things are appearing to be good :) [oliva...@localhost linux-2.6.30]$ cd .. [oliva...@localhost Download]$ cp patch-2.6.30.1.bz2 linux-2.6.30/ [oliva...@localhost Download]$ cd linux-2.6.30 [oliva...@localhost linux-2.6.30]$ make mrproper CLEAN arch/x86/boot/compressed CLEAN arch/x86/boot CLEAN /home/olivares/Download/linux-2.6.30 CLEAN arch/x86/kernel/acpi/realmode CLEAN arch/x86/kernel/cpu CLEAN arch/x86/kernel CLEAN arch/x86/vdso CLEAN drivers/char CLEAN drivers/md CLEAN drivers/scsi/aic7xxx CLEAN drivers/video/logo CLEAN firmware CLEAN init CLEAN kernel CLEAN lib CLEAN usr CLEAN Documentation/accounting CLEAN Documentation/auxdisplay CLEAN Documentation/connector CLEAN Documentation/ia64 CLEAN Documentation/networking CLEAN Documentation/pcmcia CLEAN Documentation/spi CLEAN Documentation/video4linux CLEAN Documentation/vm CLEAN Documentation/watchdog/src CLEAN .tmp_versions CLEAN vmlinux System.map .tmp_kallsyms1.o .tmp_kallsyms1.S .tmp_kallsyms2.o .tmp_kallsyms2.S .tmp_kallsyms3.o .tmp_kallsyms3.S .tmp_vmlinux1 .tmp_vmlinux2 .tmp_vmlinux3 .tmp_System.map CLEAN scripts/basic CLEAN scripts/kconfig CLEAN scripts/mod CLEAN scripts/selinux/mdp CLEAN scripts CLEAN include/config usr/include CLEAN .config .config.old include/asm .version include/linux/autoconf.h include/linux/version.h include/linux/utsrelease.h include/linux/bounds.h include/asm/asm-offsets.h include/asm-x86/asm-offsets.h Module.symvers Module.markers [oliva...@localhost linux-2.6.30]$ bunzip2 patch-2.6.30.1.bz2 [oliva...@localhost linux-2.6.30]$ ls arch Documentation initMAINTAINERS README sound blockdriversipc MakefileREPORTING-BUGS usr COPYING firmware Kbuild mm samples virt CREDITS fs kernel net scripts crypto includelib patch-2.6.30.1 security [oliva...@localhost linux-2.6.30]$ patch -P1 patch-2.6.30.1 patch: invalid option -- 'P' patch: Try `patch --help' for more information. [oliva...@localhost linux-2.6.30]$ patch -p1 patch-2.6.30.1 patching file Documentation/sysctl/vm.txt patching file Makefile patching file arch/arm/include/asm/cacheflush.h patching file arch/x86/crypto/aesni-intel_asm.S patching file arch/x86/include/asm/apic.h patching file arch/x86/include/asm/cpufeature.h patching file arch/x86/include/asm/kvm_host.h patching file arch/x86/include/asm/mce.h patching file arch/x86/include/asm/uv/uv_bau.h patching file arch/x86/include/asm/uv/uv_hub.h patching file arch/x86/include/asm/vmx.h patching file arch/x86/kernel/apic/x2apic_uv_x.c patching file arch/x86/kernel/cpu/amd.c patching file arch/x86/kernel/cpu/mcheck/mce_32.c patching file arch/x86/kernel/cpu/mcheck/mce_64.c patching file arch/x86/kernel/hpet.c patching file arch/x86/kernel/pci-gart_64.c patching file arch/x86/kernel/reboot.c patching file arch/x86/kernel/setup.c patching file arch/x86/kernel/tlb_uv.c patching file arch/x86/kernel/tsc.c patching file arch/x86/kernel/vm86_32.c patching file arch/x86/kernel/vsyscall_64.c patching file arch/x86/kvm/vmx.c patching file arch/x86/kvm/x86.c patching file arch/x86/mm/memtest.c patching file drivers/char/epca.c patching file drivers/char/moxa.c patching file drivers/char/n_r3964.c patching file drivers/char/pcmcia/cm4000_cs.c patching file drivers/char/rocket.c patching file drivers/char/vt_ioctl.c patching file drivers/firmware/memmap.c patching file drivers/gpu/drm/i915/i915_drv.c patching file drivers/ide/ide-cd.c patching file drivers/infiniband/hw/mlx4/qp.c patching file drivers/isdn/hisax/hfc_pci.c patching file drivers/isdn/hisax/hisax.h patching file drivers/md/dm-exception-store.c patching file drivers/md/dm-exception-store.h patching file drivers/md/dm-log.c patching file drivers/md/dm-mpath.c patching file drivers/md/dm-table.c patching file drivers/md/dm.c patching file drivers/md/raid5.c patching file drivers/media/dvb/frontends/lgdt3305.c patching file drivers/media/video/Makefile patching file drivers/media/video/cx18/cx18-controls.c patching file drivers/media/video/cx2341x.c patching file drivers/media/video/ivtv/ivtv-controls.c patching file drivers/media/video/pvrusb2/pvrusb2-hdw.c patching file drivers/media/video/saa7134/Makefile patching file drivers/net/bonding/bond_sysfs.c patching file
Re: kernel 2.6.30.1
--- On Fri, 7/3/09, Mail Lists li...@sapience.com wrote: From: Mail Lists li...@sapience.com Subject: kernel 2.6.30.1 To: Community assistance, encouragement, and advice for using Fedora. fedora-list@redhat.com Date: Friday, July 3, 2009, 7:47 AM 2.6.30.1 is the recommended stable kernel by upstream - are there plans to make this available for f10 and f11 ?? Both f10 and f11 are more lagging than the past it seems - probably with the release of f11. I didnt find much in koji ... As per linux-kernel mailing list: 1) 2.6.29.6 NOTE This is the last release of the 2.6.29 kernel series. All users are strongly suggested to move to the 2.6.30 release series at this time. 2) announcing the release of the 2.6.30.1 kernel. All users of the 2.6.30 kernel series are very strongly encouraged to upgrade. -- I hear you and I am applying the patch from 2.6.30 to 2.6.30.1 as of now. I know your frustrations, but Fedora is staying a bit behind as of now because apparently many things were changed from 2.6.29 to 2.6.30? I don't know the exact reasons, but I understand where you are coming from and I agree with you. Is Fedora countering the saying Latest and Greatest? I know that on rawhide a 2.6.31.rcX kernel is being run, that is where the latest and greatest always is, but Fedora Stable should not be so far behind? Should it? Regards, Antonio -- 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.30
I will come back in about an 1 hour or 2 and post if I have 2.6.30.1 kernel or not. Thanks for the help and encouragement :) Regards, Antonio -- To add closure to this thread, Thank you Mr. John Wendel, your instructions worked and I am now running 2.6.31 on a Fedora 10 machine. I am grateful to you and all others that helped me answer this and other questions about kernels. [oliva...@localhost ~]$ uname -r 2.6.30.1 [oliva...@localhost ~]$ uname -a Linux localhost.localdomain 2.6.30.1 #1 SMP Fri Jul 3 10:37:01 CDT 2009 i686 i686 i386 GNU/Linux Regards, Antonio -- 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.30
Antonio Olivares wrote: If kernel.org releases 2.6.30.1, Are there any delta *.tar.gz's that one can download instead of downloading the full kernel source again to update to 2.6.30.1? I have been yearning to ask this question, but never had the courage or the determination to do so. I generally follow Fedora kernels, but sometimes I get eager to run the latest and greatest. I run rawhide too, but they are at 2.6.30-6.fc12. Someone told me that there were patches that one could download and recompile to get the latest version, but they don't tell me how and there does not seem to exist documentation as to how to do it. All of this in case Fedora stays a little bit behind, they are doing the right thing though testing and making sure that the kernels work :), and that the changes upstream do not affect the endusers in a bad way. Regards, Antonio How to patch the Linux kernel Download the latest patch file for the kernel you're running - You'll see it on the kernel.org website. Put the patch file in the directory with the original, unpatched kernel source. Run make mrproper. Run bunzip to uncompress the patch file. Run patch -P1 patch-file-name Now your kernel is patched to the latest version. Do your kernel build. http://www.kernel.org/pub/linux/kernel/v2.6/patch-2.6.30.1.bz2 Patch is out for 2.6.30.1, how exactly do I do it. I run patch -P1 patch-2.6.30.1.bz2 in /linux-2.6.30 directory where the 2.6.30 source was? Do I extract the patch? This is where I need more guidance as I have not done it. Usually I just get the entire thing 2.6.30.1.tar.bz2 but now I don't have access to high speed connection and I just want to see if I can do it. You want to uncompress the patch, either in place or via a pipe: bzcat ../patch-2.6.30.1.bz2 | patch -p1 I highly recommend adding --dry-run to the patch command the first time, and watching for errors. Note that I normally put the patches in the parent directory (..) so adjust to fit your needs. Also note you are building a kernel.org kernel, not a Fedora kernel, there are some times when the Fedora kernel has patches not in mainline. I generally try my kernels in a VM before I go with them for real. -- Bill Davidsen david...@tmr.com 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: kernel 2.6.30.1
Antonio Olivares wrote: --- On Fri, 7/3/09, Mail Lists li...@sapience.com wrote: From: Mail Lists li...@sapience.com Subject: kernel 2.6.30.1 To: Community assistance, encouragement, and advice for using Fedora. fedora-list@redhat.com Date: Friday, July 3, 2009, 7:47 AM 2.6.30.1 is the recommended stable kernel by upstream - are there plans to make this available for f10 and f11 ?? Both f10 and f11 are more lagging than the past it seems - probably with the release of f11. I didnt find much in koji ... As per linux-kernel mailing list: 1) 2.6.29.6 NOTE This is the last release of the 2.6.29 kernel series. All users are strongly suggested to move to the 2.6.30 release series at this time. 2) announcing the release of the 2.6.30.1 kernel. All users of the 2.6.30 kernel series are very strongly encouraged to upgrade. -- I hear you and I am applying the patch from 2.6.30 to 2.6.30.1 as of now. I know your frustrations, but Fedora is staying a bit behind as of now because apparently many things were changed from 2.6.29 to 2.6.30? I think that sums it up, with any new release there will be a surge of issues, most minor, as new users migrate. Better to fix most of these before adding the features of a new kernel to the mix. I don't know the exact reasons, but I understand where you are coming from and I agree with you. Is Fedora countering the saying Latest and Greatest? I knowthat on rawhide a 2.6.31.rcX kernel is being run, that is where the latest and greatest always is, but Fedora Stable should not be so far behind? Should it? Remember that latest and greatest are not synonyms, there were many changes in 2.6.30, and a little time for shakeout is a good thing. People are just getting used to ext4, adding a number of new filesystem types is likely to cause more questions, and probably will mean updates of the utilities for the filesystems as well. I think Fedora is moving at the right speed on this one, you can build your own, or pull from testing, or rawhide, or koji, depending on your tolerance for learning experiences. -- Bill Davidsen david...@tmr.com 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: kernel 2.6.30.1
I hear you and I am applying the patch from 2.6.30 to 2.6.30.1 as of now. I know your frustrations, but Fedora is staying a bit behind as of now because apparently many things were changed from 2.6.29 to 2.6.30? I think that sums it up, with any new release there will be a surge of issues, most minor, as new users migrate. Better to fix most of these before adding the features of a new kernel to the mix. I don't know the exact reasons, but I understand where you are coming from and I agree with you. Is Fedora countering the saying Latest and Greatest? I knowthat on rawhide a 2.6.31.rcX kernel is being run, that is where the latest and greatest always is, but Fedora Stable should not be so far behind? Should it? Remember that latest and greatest are not synonyms, there were many changes in 2.6.30, and a little time for shakeout is a good thing. People are just getting used to ext4, adding a number of new filesystem types is likely to cause more questions, and probably will mean updates of the utilities for the filesystems as well. I think Fedora is moving at the right speed on this one, you can build your own, or pull from testing, or rawhide, or koji, depending on your tolerance for learning experiences. -- Bill Davidsen david...@tmr.com We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot -- fedora-list mailing list Just as an example, I tried to update to 2.6.30.1 kernel on a Fedora 11 system and I get the following: [oliva...@black-amd64-home linux-2.6.30]$ cat /etc/fedora-release Fedora release 11 (Leonidas) [oliva...@black-amd64-home linux-2.6.30]$ uname -r 2.6.30 ... include/linux/backing-dev.h:205: warning: ‘struct page’ declared inside parameter list include/linux/backing-dev.h:205: warning: its scope is only this definition or declaration, which is probably not what you want In file included from include/linux/blkdev.h:17, from include/scsi/scsi_device.h:9, from drivers/scsi/qla4xxx/ql4_def.h:32, from drivers/scsi/qla4xxx/ql4_init.c:10: include/linux/bio.h: In function ‘bio_data’: include/linux/bio.h:232: warning: passing argument 1 of ‘lowmem_page_address’ from incompatible pointer type include/linux/mm.h:597: note: expected ‘struct ��ދ� *’ but argument is of type ‘struct page *’ In file included from include/linux/blkdev.h:17, from include/scsi/scsi_device.h:9, from drivers/scsi/qla4xxx/ql4_def.h:32, from drivers/scsi/qla4xxx/ql4_init.c:10: include/linux/bio.h: In function ‘__bio_kmap_irq’: include/linux/bio.h:492: warning: passing argument 1 of ‘lowmem_page_address’ from incompatible pointer type include/linux/mm.h:597: note: expected ‘struct ��ދ� *’ but argument is of type ‘struct page *’ In file included from include/scsi/scsi_device.h:9, from drivers/scsi/qla4xxx/ql4_def.h:32, from drivers/scsi/qla4xxx/ql4_init.c:10: include/linux/blkdev.h: In function ‘blk_run_backing_dev’: include/linux/blkdev.h:825: warning: passing argument 2 of ‘bdi-unplug_io_fn’ from incompatible pointer type include/linux/blkdev.h:825: note: expected ‘struct ��ދ� *’ but argument is of type ‘struct page *’ In file included from include/scsi/scsi_device.h:9, from drivers/scsi/qla4xxx/ql4_def.h:32, from drivers/scsi/qla4xxx/ql4_init.c:10: include/linux/blkdev.h: In function ‘put_dev_sector’: include/linux/blkdev.h:1019: warning: passing argument 1 of ‘put_page’ from incompatible pointer type include/linux/mm.h:323: note: expected ‘struct ��ދ� *’ but argument is of type ‘struct page *’ drivers/scsi/qla4xxx/ql4_init.c: In function ‘qla4xxx_free_ddb_list’: drivers/scsi/qla4xxx/ql4_init.c:81: error: ‘struct list_head’ has no member named ‘next’ drivers/scsi/qla4xxx/ql4_init.c: In function ‘qla4xxx_get_ddb_entry’: drivers/scsi/qla4xxx/ql4_init.c:344: error: ‘struct list_head’ has no member named ‘next’ drivers/scsi/qla4xxx/ql4_init.c:344: error: ‘struct list_head’ has no member named ‘next’ drivers/scsi/qla4xxx/ql4_init.c:344: error: ‘struct list_head’ has no member named ‘next’ drivers/scsi/qla4xxx/ql4_init.c: In function ‘qla4xxx_reinitialize_ddb_list’: drivers/scsi/qla4xxx/ql4_init.c:800: error: ‘struct list_head’ has no member named ‘next’ drivers/scsi/qla4xxx/ql4_init.c:800: error: ‘struct list_head’ has no member named ‘next’ drivers/scsi/qla4xxx/ql4_init.c:800: error: ‘struct list_head’ has no member named ‘next’ drivers/scsi/qla4xxx/ql4_init.c:1250: confused by earlier errors, bailing out The bug is not reproducible, so it is likely a hardware or OS problem. make[3]: *** [drivers/scsi/qla4xxx/ql4_init.o] Error 1 make[2]: *** [drivers/scsi/qla4xxx] Error 2 make[1]: *** [drivers/scsi] Error 2 make: *** [drivers] Error 2 [oliva...@black-amd64-home linux-2.6.30]$ I have not encountered these before,
