PDA

View Full Version : kernel-2.6.17 Pulled?



lazlow
1st July 2006, 06:31 AM
Hey Guys

I have been holding off on updating to 2.6.17 until a few of the bugs have been cleaned up. I noticed tonight when I did a yum check-update that it did not come up. When I did a yum info kernel, 2133 was what came up.(one for on system and one for updates). I was just wondering if it was pulled due to all the bugs?

Lazlow

Seve
1st July 2006, 07:34 AM
Hello:
Could be? I dunno for sure as the source.rpm is still there on http://download.fedora.redhat.com/pub/fedora/linux/core/updates/5/SRPMS/
I checked a couple of mirror and that kernel is still listed, however it doesn't mean that you are not correct as the syncing of all the mirrors can sometimes be an issue.
Seve

marcrblevins
1st July 2006, 08:02 AM
Not pulled.

Did:
yum remove kernel-2.6.17-1.2139_FC5

Then:
yum update
It found:
kernel i686 2.6.17-1.2139_FC5 updates 15 M

"My system hangs at Making device-mapper control node", just after that, "dmraid -tay" was suppose to perform with 2139 release.

I spent most of the night going over 2139 version. I stronly believe it doesn't have dmraid built in. I tried to build my own kernel, but was confused with where to get the .config file and modify the Makefile. I'll just wait til its fix in future kernel updates. Have to remember not to reboot my system and leave. Use 2133 for now.

Wayne
1st July 2006, 08:06 AM
Hey Guys

I have been holding off on updating to 2.6.17 until a few of the bugs have been cleaned up. I noticed tonight when I did a yum check-update that it did not come up. When I did a yum info kernel, 2133 was what came up.(one for on system and one for updates). I was just wondering if it was pulled due to all the bugs?

Lazlow

Maybe I've been asleep or not reading much but what bugs? I'm using it on two machines and I haven't noticed anything. Now I'm worried that I may have a buggy kernel. :eek:

Wayne

psyklops
1st July 2006, 11:48 AM
it runs fine on my AMD 3200 here with 2GB RAM and Nvidia card.

However, it killed a friends laptop and a PC at work. the previous kernel works... there's some issues with it...

jbannon
1st July 2006, 12:21 PM
Works fine on my I845 Pentium 4 as well. I've not noticed any issues, that is none that I javen't had with FC5 generally.

CrystalCowboy
1st July 2006, 03:06 PM
2.6.17-1.2139_FC5 seems to be running OK on one of my machines. I did a yum check-update on another, and 2.6.17-1.2139_FC4 shows up.

My primary desktop machine, with a Socket A thlon and FC4, has not booted properly under any kernel version 2.6.16 or 2.6.17. Something to do with IRQs. I still have to run 2.6.15-1.1833_FC4 on that one.

commonplace
1st July 2006, 10:00 PM
I can't seem to update to the new 2139 kernel. It doesn't come up under Software Updater, and when I use the CLI to run 'yum update kernel', it says:


Could not find update match for kernel
No Packages marked for Update/Obsoletion

If I do 'yum info kernel', though, I see the 2139 kernel.

What am I doing wrong? I'm still pretty much a newbie, and this is the first time I haven't been able to update the kernel (usually I just use the Software Updater (pup)).

lazlow
1st July 2006, 11:45 PM
Well I do not know what the deal was it showed up last week, it shows up now, but it sure did not show up last night.

As far as the bugs go: just search the forum for 2.6.17 it seems like a lot of strange stuff relating to the kernel (could be I just noticed it with this kernel).

commanplace

Do uname -r in terminal. Maybe you have already updated (I have done stuff like that before).

At any rate, thanks to all.

Lazlow

commonplace
1st July 2006, 11:52 PM
lazlow, I did uname -r and it shows I'm on 2133, which is correct. I still don't know why I can't update to 2139.

Wayne
1st July 2006, 11:53 PM
I can't seem to update to the new 2139 kernel. It doesn't come up under Software Updater, and when I use the CLI to run 'yum update kernel', it says:



If I do 'yum info kernel', though, I see the 2139 kernel.

What am I doing wrong? I'm still pretty much a newbie, and this is the first time I haven't been able to update the kernel (usually I just use the Software Updater (pup)).

If you really want it you can get it here, older ones are there too:

http://download.fedora.redhat.com/pub/fedora/linux/core/updates/5/i386/

Wayne

commonplace
2nd July 2006, 01:46 AM
If you really want it you can get it here, older ones are there too:

http://download.fedora.redhat.com/pub/fedora/linux/core/updates/5/i386/

Wayne

Alright, when I try to install the new kernel, rpm says:


package kernel-2.6.17-1.2139_FC5 is already installed


When I try to remove the rpm (rpm -e), it says:


error: package kernel-2.6.17-1.2139_FC5.i686.rpm is not installed


The new 2139 is not listed as an option on the bootup menu, and I don't see it listed in /boot (I see 2122 and 2133, but not 2139).

I tried rpm --rebuilddb, but it didn't help. What do I do now? RPM, PUP, etc. think the new kernel is installed... but it's not.

lazlow
2nd July 2006, 02:53 AM
Commonplace

I have not seen anything like this before. Try yum remove full-kernel-name ? You could install smartPM and try its check installed packages (it has gotten me out of a couple of box canyons before). If that fails you could try its reinstall function.

?????

lazlow

idiotprogrammer
2nd July 2006, 04:35 AM
When I upgraded to 2139, I had a major power management issue.
http://forum.fedoraforum.org/showthread.php?t=115673

Personally, I'd send this kernel back to hell.

dewangpm
2nd July 2006, 06:34 AM
lazlow, I did uname -r and it shows I'm on 2133, which is correct. I still don't know why I can't update to 2139.

because you may be using SMP like this 2.6.16-1.2133_FC5smp i686

dewang

timdahl
3rd July 2006, 11:49 PM
I have also had problems with 2.6.17-1.2139_FC5 (FC5_x86_64 running on dell precision 380; pentiumD, Nvidia Quadro NVS 285; SATA [fake]RAID 1; . I simply did my routine yum update, and found that when booting new kernel (2.6.17) it hangs with following error:

int[1] trap divide error rip:4296d7 rsp:7fff0d304bd0 error:0

I noticed another thread commenting on this error as if it was a miscompile, which is clearly not the case for me.

For now I will run the 2.6.16, but am fishing for more info on the 2.6.17 error(s?) I have seen.

Any insight appreciated.
Oh... and yes, this is my first post here, but read it on a regular basis. I figured that now I am responsible for multiple linux boxes at my place of employment (running fedora core) I should be more interactive.

-tim

A.Serbinski
5th July 2006, 06:54 PM
For that trap divide error...

FAKE RAID is at the root of the problem. It is Fedora specific.
It has to do with how Fedora handles fake raid.

Temporary work around:
Extract your /boot/initrd-2.6.17.whatever.img
Modify the init file in it to comment out any line that starts with "dm partadd",
Then put it back together in /boot/initrd-.....img

In case you don't know how to work with the initrd.img file, here's a thread on it;
http://www.fedoraforum.org/forum/showthread.php?t=114819

timdahl
5th July 2006, 10:00 PM
I tried the initrd fix, but it failed to bood because it could not recognize the logical volumes (resulting in a kernel panic), presumably because the FAKERAID was needed to find the boot image. I supose its sloppy to have my boot partition mirrored by fakeraid....

A.Serbinski
5th July 2006, 11:35 PM
At what point did the kernel panic happen? Before or after starting nash? Are you sure that you created the new initrd.img correctly? The cpio format is NOT default, it is 'newc' - if this is neglected, it WILL result in a kernel panic, specifically, BEFORE nash, it would give a root fs mount error.

If its a fakeraid MIRROR, you should be able to ignore it. The problem with this though, is that you have to change all references to the fakeraid device to the real device, that is, assuming that you would prefer to use 2.6.17 NOW over keeping your fakeraid mirror. You will also have to mkinitrd and redo the initrd.img modifications after you change all the references. Hopefully though, the bug will be worked out soon and you won't have to do this.

timdahl
6th July 2006, 12:36 AM
I believe it crashed after nash (although I am not positive), and I am sure that the repackaged initrd file was done correctly (I did use newc) because I did the identical process to my 2.6.16 kernel and simply added a blank comment (as a control) with no problems.

I am not interested at momoent in screwing around with all the dmraid workarounds at this point.... for now, will just use 2.6.16... as they say, if it ain't broke, don't fix it. (I only did my update because it was routine every month... I was having no problems with my desktop prior).

thanks for your tips though, made a note of them and if I get into a pinch, will give another try.

thanks
-tim

Wayne
6th July 2006, 03:31 AM
New kernel updated today:

2.6.17-1.2145_FC5

Wayne

A.Serbinski
6th July 2006, 03:54 AM
If this is the same 2145 that was in testing from the 3rd, then the bug is still present.

name_user
6th July 2006, 02:38 PM
I just updated to 2145. Same problem as 2139: After starting up, no log in screen shows up, and the screen goes into blank. My computer: HP Pavilion zd8100us, Memory 1.0 G, CPU: P4 3.0G, Harddisk 100 G, and ATI mobility Radeon X600. Any advices are appreciated.

qinhan
6th July 2006, 02:51 PM
I'm wonder why they put the kernerl update out knowing there are problems with it.

sentry
6th July 2006, 02:57 PM
Perhaps because the issues affect a small percentage of the user base?

name_user
6th July 2006, 03:06 PM
Below are the messages logged during starting up:

Jul 6 09:41:05 syslogd 1.4.1: restart.
Jul 6 09:41:06 kernel: klogd 1.4.1, log source = /proc/kmsg started.
Jul 6 09:41:06 kernel: Linux version 2.6.17-1.2145_FC5smp (brewbuilder@hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)) #1 SMP Sat Jul 1 13:19:14 EDT 2006
Jul 6 09:41:06 kernel: BIOS-provided physical RAM map:
Jul 6 09:41:06 kernel: BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
Jul 6 09:41:06 kernel: BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
Jul 6 09:41:06 kernel: BIOS-e820: 00000000000d8000 - 00000000000e0000 (reserved)
Jul 6 09:41:06 kernel: BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
Jul 6 09:41:06 kernel: BIOS-e820: 0000000000100000 - 000000003fef0000 (usable)
Jul 6 09:41:06 kernel: BIOS-e820: 000000003fef0000 - 000000003fef9000 (ACPI data)
Jul 6 09:41:06 kernel: BIOS-e820: 000000003fef9000 - 000000003ff00000 (ACPI NVS)
Jul 6 09:41:06 kernel: BIOS-e820: 000000003ff00000 - 0000000040000000 (reserved)
Jul 6 09:41:06 kernel: BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
Jul 6 09:41:06 kernel: BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
Jul 6 09:41:06 kernel: 126MB HIGHMEM available.
Jul 6 09:41:07 kernel: 895MB LOWMEM available.
Jul 6 09:41:07 rpc.statd[1988]: Version 1.0.8-rc2 Starting
Jul 6 09:41:08 kernel: found SMP MP-table at 000f7a70
Jul 6 09:41:09 kernel: NX (Execute Disable) protection: active
Jul 6 09:41:11 hcid[2042]: Bluetooth HCI daemon
Jul 6 09:41:12 sdpd[2045]: Bluetooth SDP daemon
Jul 6 09:41:12 kernel: DMI present.
Jul 6 09:41:13 kernel: Using APIC driver default
Jul 6 09:41:13 hidd[2113]: Bluetooth HID daemon
Jul 6 09:41:14 kernel: ACPI: PM-Timer IO Port: 0x1008
Jul 6 09:41:14 kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 6 09:41:14 kernel: Processor #0 15:4 APIC version 20
Jul 6 09:41:14 kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 6 09:41:14 kernel: Processor #1 15:4 APIC version 20
Jul 6 09:41:14 kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 6 09:41:14 kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 6 09:41:14 kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
Jul 6 09:41:14 kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Jul 6 09:41:14 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
Jul 6 09:41:14 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 6 09:41:14 kernel: Enabling APIC mode: Flat. Using 1 I/O APICs
Jul 6 09:41:14 kernel: Using ACPI (MADT) for SMP configuration information
Jul 6 09:41:14 kernel: Allocating PCI resources starting at 50000000 (gap: 40000000:bec00000)
Jul 6 09:41:14 kernel: Built 1 zonelists
---to be continued---

tfindlay
6th July 2006, 03:09 PM
I recently upgraded to 2.6.17.2319 which caused me no end of grief.

Firstly theres this message about "MCFG BIOS BUG" ?!? I've got an ASUS P5WD2 and already have the latest bios, what am I supposed to do about it ?!?
Then I started getting all these errors about "Interface /dev/xxxxx not found" ... this problem seems to be related to my 2 on-board ethernet controllers. I subsequently spent frigg'n hours messing with these and have still only managed to get the Intel controller working as ETH2, the Marvell controller just wont work under this kernel.

On a final note, I've just YUM'd a 2.6.17-1.2141 kernel .... I'm too paranoid to reboot and try it out just yet, I think I'll wait till the weekend when I've got some time to coax it into working.

PS. 2141 must be new as theres no nviidia or NTFS pacakegs for it on Livna yet (that I can see at least)

PPS. I should also note I'm still on FC4 too. Waiting for FC6 before my next wipeout.

name_user
6th July 2006, 03:10 PM
Jul 6 09:41:14 kernel: Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet
Jul 6 09:41:14 kernel: Enabling fast FPU save and restore... done.
Jul 6 09:41:14 smartd[2214]: smartd version 5.36 [i686-redhat-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Jul 6 09:41:14 kernel: Enabling unmasked SIMD FPU exception support... done.
Jul 6 09:41:14 kernel: Initializing CPU#0
Jul 6 09:41:14 kernel: CPU 0 irqstacks, hard=c07ad000 soft=c078d000
Jul 6 09:41:14 kernel: PID hash table entries: 4096 (order: 12, 16384 bytes)
Jul 6 09:41:14 smartd[2214]: Home page is http://smartmontools.sourceforge.net/
Jul 6 09:41:14 kernel: Detected 2992.891 MHz processor.
Jul 6 09:41:14 smartd[2214]: Opened configuration file /etc/smartd.conf
Jul 6 09:41:14 kernel: Using pmtmr for high-res timesource
Jul 6 09:41:14 kernel: Console: colour VGA+ 80x25
Jul 6 09:41:14 kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Jul 6 09:41:14 kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Jul 6 09:41:14 smartd[2214]: Configuration file /etc/smartd.conf parsed.
Jul 6 09:41:14 kernel: Memory: 1029584k/1047488k available (2150k kernel code, 17176k reserved, 1200k data, 244k init, 129988k highmem)
Jul 6 09:41:14 smartd[2214]: Device: /dev/hda, opened
Jul 6 09:41:14 kernel: Checking if this processor honours the WP bit even in supervisor mode... Ok.
Jul 6 09:41:14 smartd[2214]: Device: /dev/hda, found in smartd database.
Jul 6 09:41:14 kernel: Calibrating delay using timer specific routine.. 5993.01 BogoMIPS (lpj=11986022)
Jul 6 09:41:14 kernel: Security Framework v1.0.0 initialized
Jul 6 09:41:15 smartd[2214]: Device: /dev/hda, is SMART capable. Adding to "monitor" list.
Jul 6 09:41:15 kernel: SELinux: Initializing.
Jul 6 09:41:15 smartd[2214]: Monitoring 1 ATA and 0 SCSI devices
Jul 6 09:41:15 kernel: SELinux: Starting in permissive mode
Jul 6 09:41:15 kernel: selinux_register_security: Registering secondary module capability
Jul 6 09:41:15 smartd[2216]: smartd has fork()ed into background mode. New PID=2216.
Jul 6 09:41:15 kernel: Capability LSM initialized as secondary
Jul 6 09:41:15 kernel: Mount-cache hash table entries: 512
Jul 6 09:41:15 kernel: monitor/mwait feature present.
Jul 6 09:41:15 hpiod: 0.9.11 accepting connections at 50000...
Jul 6 09:41:15 kernel: using mwait in idle threads.
Jul 6 09:41:15 kernel: CPU: Trace cache: 12K uops, L1 D cache: 16K
Jul 6 09:41:16 kernel: CPU: L2 cache: 2048K
Jul 6 09:41:16 kernel: CPU: Physical Processor ID: 0
Jul 6 09:41:16 kernel: Intel machine check architecture supported.
Jul 6 09:41:16 kernel: Intel machine check reporting enabled on CPU#0.
Jul 6 09:41:16 kernel: CPU0: Intel P4/Xeon Extended MCE MSRs (24) available
Jul 6 09:41:16 kernel: Checking 'hlt' instruction... OK.
Jul 6 09:41:16 kernel: SMP alternatives: switching to UP code
Jul 6 09:41:16 kernel: CPU0: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 03
Jul 6 09:41:16 kernel: SMP alternatives: switching to SMP code
Jul 6 09:41:16 kernel: Booting processor 1/1 eip 3000
Jul 6 09:41:16 kernel: CPU 1 irqstacks, hard=c07ae000 soft=c078e000
----To be continued---

name_user
6th July 2006, 03:15 PM
Jul 6 09:41:16 kernel: Initializing CPU#1
Jul 6 09:41:16 kernel: Calibrating delay using timer specific routine.. 5985.45 BogoMIPS (lpj=11970916)
Jul 6 09:41:17 kernel: monitor/mwait feature present.
Jul 6 09:41:17 kernel: CPU: Trace cache: 12K uops, L1 D cache: 16K
Jul 6 09:41:17 kernel: CPU: L2 cache: 2048K
Jul 6 09:41:17 kernel: CPU: Physical Processor ID: 0
Jul 6 09:41:17 kernel: Intel machine check architecture supported.
Jul 6 09:41:17 kernel: Intel machine check reporting enabled on CPU#1.
Jul 6 09:41:17 kernel: CPU1: Intel P4/Xeon Extended MCE MSRs (24) available
Jul 6 09:41:17 kernel: CPU1: Thermal monitoring enabled
Jul 6 09:41:17 kernel: CPU1: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 03
Jul 6 09:41:17 kernel: Total of 2 processors activated (11978.46 BogoMIPS).
Jul 6 09:41:17 kernel: ENABLING IO-APIC IRQs
Jul 6 09:41:17 kernel: ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 6 09:41:17 kernel: checking TSC synchronization across 2 CPUs: passed.
Jul 6 09:41:17 kernel: Brought up 2 CPUs
Jul 6 09:41:17 kernel: migration_cost=8000
Jul 6 09:41:17 kernel: checking if image is initramfs... it is
Jul 6 09:41:17 kernel: Freeing initrd memory: 1664k freed
Jul 6 09:41:17 kernel: NET: Registered protocol family 16
Jul 6 09:41:17 kernel: ACPI: bus type pci registered
Jul 6 09:41:17 kernel: PCI: BIOS Bug: MCFG area is not E820-reserved
Jul 6 09:41:17 kernel: PCI: Not using MMCONFIG.
Jul 6 09:41:17 kernel: PCI: PCI BIOS revision 2.10 entry at 0xfd95e, last bus=11
Jul 6 09:41:17 kernel: Setting up standard PCI resources
Jul 6 09:41:17 kernel: ACPI: Subsystem revision 20060127
Jul 6 09:41:18 kernel: ACPI: Interpreter enabled
Jul 6 09:41:18 kernel: ACPI: Using IOAPIC for interrupt routing
Jul 6 09:41:18 kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
Jul 6 09:41:18 kernel: PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
Jul 6 09:41:18 kernel: PCI: Transparent bridge - 0000:00:1e.0
Jul 6 09:41:19 kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 *10 11 14 15)
Jul 6 09:41:19 kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 10 11 14 15) *5
Jul 6 09:41:19 kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 10 *11 14 15)
Jul 6 09:41:19 kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 10 11 14 15) *7
Jul 6 09:41:19 kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 10 11 14 15) *7
Jul 6 09:41:19 kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 10 11 14 15) *0, disabled.
Jul 6 09:41:19 kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 10 *11 14 15)
Jul 6 09:41:19 kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 10 11 14 15) *7
Jul 6 09:41:19 kernel: ACPI: Embedded Controller [EC0] (gpe 29) interrupt mode.
Jul 6 09:41:19 kernel: Linux Plug and Play Support v0.97 (c) Adam Belay
Jul 6 09:41:19 kernel: pnp: PnP ACPI init
Jul 6 09:41:19 kernel: pnp: PnP ACPI: found 9 devices
Jul 6 09:41:19 kernel: usbcore: registered new driver usbfs
Jul 6 09:41:19 kernel: usbcore: registered new driver hub
---To be continued---

Firewing1
6th July 2006, 03:18 PM
Well, kernel-2.6.17-1.2145_FC5 just came out, maybe that one's better.
As for the dmraid and makefile modifying (I know that post was a while back) there's an excellent howto in the howto section about compiling kernels, and basically download your source from kernel.org, extract it, and run:

make mrproper
make oldconfig
su -
yum install ncurses-devel
exit
make menuconfig
edit your options
make rpm-pkg
I think that should do it.
Firewing1

name_user
6th July 2006, 03:20 PM
Jul 6 09:41:19 kernel: PCI: Using ACPI for IRQ routing
Jul 6 09:41:19 kernel: PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
Jul 6 09:41:19 kernel: PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.0
Jul 6 09:41:19 kernel: PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.0
Jul 6 09:41:19 kernel: PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.0
Jul 6 09:41:19 kernel: PCI: Bridge: 0000:00:01.0
Jul 6 09:41:19 kernel: IO window: 4000-4fff
Jul 6 09:41:19 kernel: MEM window: c8100000-c81fffff
Jul 6 09:41:19 kernel: PREFETCH window: d0000000-d7ffffff
Jul 6 09:41:20 kernel: PCI: Bridge: 0000:00:1c.0
Jul 6 09:41:20 kernel: IO window: disabled.
Jul 6 09:41:20 kernel: MEM window: disabled.
Jul 6 09:41:20 kernel: PREFETCH window: disabled.
Jul 6 09:41:20 gpm[2330]: *** info [startup.c(95)]:
Jul 6 09:41:20 kernel: PCI: Bus 12, cardbus bridge: 0000:0b:00.0
Jul 6 09:41:20 kernel: IO window: 00005400-000054ff
Jul 6 09:41:20 gpm[2330]: Started gpm successfully. Entered daemon mode.
Jul 6 09:41:20 kernel: IO window: 00005800-000058ff
Jul 6 09:41:21 kernel: PREFETCH window: 50000000-51ffffff
Jul 6 09:41:21 kernel: MEM window: 52000000-53ffffff
Jul 6 09:41:21 kernel: PCI: Bridge: 0000:00:1e.0
Jul 6 09:41:21 kernel: IO window: 5000-5fff
Jul 6 09:41:21 kernel: MEM window: c8200000-c82fffff
Jul 6 09:41:22 kernel: PREFETCH window: 50000000-51ffffff
Jul 6 09:41:25 kernel: ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 169
Jul 6 09:41:25 avahi-daemon[2419]: Found user 'avahi' (UID 70) and group 'avahi' (GID 70).
Jul 6 09:41:26 kernel: ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 17 (level, low) -> IRQ 177
Jul 6 09:41:26 avahi-daemon[2419]: Successfully dropped root privileges.
Jul 6 09:41:26 avahi-daemon[2419]: avahi-daemon 0.6.10 starting up.
Jul 6 09:41:26 kernel: ACPI: PCI Interrupt 0000:0b:00.0[A] -> GSI 16 (level, low) -> IRQ 169
Jul 6 09:41:26 kernel: NET: Registered protocol family 2
Jul 6 09:41:27 kernel: IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
Jul 6 09:41:27 avahi-daemon[2419]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Jul 6 09:41:27 kernel: TCP established hash table entries: 131072 (order: 9, 2621440 bytes)
Jul 6 09:41:28 kernel: TCP bind hash table entries: 65536 (order: 8, 1310720 bytes)
Jul 6 09:41:28 avahi-daemon[2419]: Successfully called chroot().
Jul 6 09:41:28 kernel: TCP: Hash tables configured (established 131072 bind 65536)
Jul 6 09:41:28 avahi-daemon[2419]: Successfully dropped remaining capabilities.
Jul 6 09:41:28 kernel: TCP reno registered
Jul 6 09:41:29 avahi-daemon[2419]: No service found in /etc/avahi/services.
Jul 6 09:41:29 kernel: Simple Boot Flag at 0x36 set to 0x1
Jul 6 09:41:29 avahi-daemon[2419]: New relevant interface eth0.IPv4 for mDNS.
Jul 6 09:41:30 kernel: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
Jul 6 09:41:30 avahi-daemon[2419]: Joining mDNS multicast group on interface eth0.IPv4 with address 132.215.20.89.
Jul 6 09:41:30 kernel: apm: disabled - APM is not SMP safe.
---To be continued

name_user
6th July 2006, 03:30 PM
Jul 6 09:41:30 kernel: audit: initializing netlink socket (disabled)
Jul 6 09:41:30 kernel: audit(1152178828.544:1): initialized
Jul 6 09:41:30 avahi-daemon[2419]: Network interface enumeration completed.
Jul 6 09:41:30 kernel: highmem bounce pool size: 64 pages
Jul 6 09:41:31 kernel: Total HugeTLB memory allocated, 0
Jul 6 09:41:31 avahi-daemon[2419]: Registering new address record for 132.215.20.89 on eth0.
Jul 6 09:41:31 kernel: VFS: Disk quotas dquot_6.5.1
Jul 6 09:41:32 avahi-daemon[2419]: Registering HINFO record with values 'I686'/'LINUX'.
Jul 6 09:41:32 kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Jul 6 09:41:33 kernel: SELinux: Registering netfilter hooks
Jul 6 09:41:34 avahi-daemon[2419]: Server startup complete. Host name is zpmei.local. Local service cookie is 595843179.
Jul 6 09:41:35 kernel: Initializing Cryptographic API
Jul 6 09:41:35 kernel: ksign: Installing public key data
Jul 6 09:41:36 kernel: Loading keyring
Jul 6 09:41:36 kernel: - Added public key 6ABA7BE07EF0E211
Jul 6 09:41:36 kernel: - User ID: Red Hat, Inc. (Kernel Module GPG key)
Jul 6 09:41:40 kernel: io scheduler noop registered
Jul 6 09:41:40 kernel: io scheduler anticipatory registered
Jul 6 09:41:40 kernel: io scheduler deadline registered
Jul 6 09:41:40 kernel: io scheduler cfq registered (default)
Jul 6 09:41:40 kernel: ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 169
Jul 6 09:41:40 kernel: assign_interrupt_mode Found MSI capability
Jul 6 09:41:40 kernel: ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 17 (level, low) -> IRQ 177
Jul 6 09:41:40 kernel: assign_interrupt_mode Found MSI capability
Jul 6 09:41:42 dhcdbd: Started up.
Jul 6 09:41:44 kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 6 09:41:45 kernel: ACPI: Processor [CPU0] (supports 8 throttling states)
Jul 6 09:41:45 kernel: ACPI: Processor [CPU1] (supports 8 throttling states)
Jul 6 09:41:45 named[2505]: starting BIND 9.3.2 -u named -t /var/named/chroot
Jul 6 09:41:45 kernel: ACPI: Thermal Zone [THRM] (59 C)
Jul 6 09:41:46 named[2505]: found 2 CPUs, using 2 worker threads
Jul 6 09:41:46 named[2505]: loading configuration from '/etc/named.conf'
Jul 6 09:41:46 named[2505]: listening on IPv4 interface lo, 127.0.0.1#53
Jul 6 09:41:46 kernel: isapnp: Scanning for PnP cards...
Jul 6 09:41:46 named[2505]: listening on IPv4 interface eth0, 132.215.20.89#53
Jul 6 09:41:46 kernel: isapnp: No Plug & Play device found
Jul 6 09:41:46 kernel: Real Time Clock Driver v1.12ac
Jul 6 09:41:46 kernel: Non-volatile memory driver v1.2
Jul 6 09:41:46 kernel: Linux agpgart interface v0.101 (c) Dave Jones
Jul 6 09:41:46 kernel: agpgart: Detected an Intel 915G Chipset.
Jul 6 09:41:46 named[2505]: command channel listening on 127.0.0.1#953
Jul 6 09:41:46 kernel: agpgart: AGP aperture is 256M @ 0x0
Jul 6 09:41:46 named[2505]: zone 0.in-addr.arpa/IN: loaded serial 42
Jul 6 09:41:46 xinetd[2268]: xinetd Version 2.3.13 started with libwrap loadavg options compiled in.
Jul 6 09:41:46 named[2505]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
---To be continued---

name_user
6th July 2006, 03:34 PM
Jul 6 09:41:46 xinetd[2268]: Started working: 0 available services
Jul 6 09:41:46 kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
Jul 6 09:41:46 named[2505]: zone 255.in-addr.arpa/IN: loaded serial 42
Jul 6 09:41:46 kernel: ACPI: PCI Interrupt 0000:00:1e.3[A] -> GSI 22 (level, low) -> IRQ 209
Jul 6 09:41:46 named[2505]: zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0.0.ip6.arpa/IN: loaded serial 1997022700
Jul 6 09:41:46 kernel: RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Jul 6 09:41:47 named[2505]: zone localdomain/IN: loaded serial 42
Jul 6 09:41:47 kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Jul 6 09:41:47 named[2505]: zone localhost/IN: loaded serial 42
Jul 6 09:41:47 kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Jul 6 09:41:47 kernel: ICH6: IDE controller at PCI slot 0000:00:1f.1
Jul 6 09:41:47 named[2505]: running
Jul 6 09:41:47 kernel: ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 217
Jul 6 09:41:47 NetworkManager: <information> starting...
Jul 6 09:41:47 kernel: ICH6: chipset revision 3
Jul 6 09:41:47 kernel: ICH6: not 100% native mode: will probe irqs later
Jul 6 09:41:47 NetworkManager: <information> eth0: Device is fully-supported using driver '8139too'.
Jul 6 09:41:47 kernel: ide0: BM-DMA at 0x3c40-0x3c47, BIOS settings: hda:DMA, hdb:DMA
Jul 6 09:41:47 NetworkManager: <information> nm_device_init(): waiting for device's worker thread to start
Jul 6 09:41:47 NetworkManager: <information> nm_device_init(): device's worker thread started, continuing.
Jul 6 09:41:47 kernel: hda: ST9100822A, ATA DISK drive
Jul 6 09:41:47 NetworkManager: <information> Now managing wired Ethernet (802.3) device 'eth0'.
Jul 6 09:41:47 kernel: hdb: TSSTcorpCD/DVDW TS-L532R, ATAPI CD/DVD-ROM drive
Jul 6 09:41:47 NetworkManager: <information> Deactivating device eth0.
Jul 6 09:41:47 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Jul 6 09:41:47 avahi-daemon[2419]: Withdrawing address record for 132.215.20.89 on eth0.
Jul 6 09:41:47 avahi-daemon[2419]: Leaving mDNS multicast group on interface eth0.IPv4 with address 132.215.20.89.
Jul 6 09:41:47 kernel: hda: max request size: 512KiB
Jul 6 09:41:47 avahi-daemon[2419]: IP_DROP_MEMBERSHIP failed: No such device
Jul 6 09:41:47 kernel: hda: 195371568 sectors (100030 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(100)
Jul 6 09:41:47 kernel: hda: cache flushes supported
Jul 6 09:41:47 avahi-daemon[2419]: iface.c: interface_mdns_mcast_join() called but no local address available.
Jul 6 09:41:47 kernel: hda: hda1 hda2 hda4 < hda5 hda6 >
Jul 6 09:41:47 avahi-daemon[2419]: Interface eth0.IPv4 no longer relevant for mDNS.
Jul 6 09:41:47 kernel: hdb: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, DMA
Jul 6 09:41:47 kernel: Uniform CD-ROM driver Revision: 3.20
Jul 6 09:41:47 kernel: ide-floppy driver 0.99.newide
Jul 6 09:41:47 firmware_helper[2595]: Loading of /lib/firmware/bcm43xx_microcode5.fw for bcm43xx driver failed: No such file or directory
Jul 6 09:41:47 kernel: ACPI: PCI Interrupt 0000:0b:00.0[A] -> GSI 16 (level, low) -> IRQ 169
Jul 6 09:41:47 kernel: Yenta: CardBus bridge found at 0000:0b:00.0 [103c:3082]
Jul 6 09:41:47 kernel: Yenta: Enabling burst memory read transactions
Jul 6 09:41:47 kernel: Yenta: Using CSCINT to route CSC interrupts to PCI
Jul 6 09:41:47 kernel: Yenta: Routing CardBus interrupts to PCI
Jul 6 09:41:47 kernel: Yenta TI: socket 0000:0b:00.0, mfunc 0x01a01b22, devctl 0x64

name_user
6th July 2006, 03:39 PM
Jul 6 09:41:47 kernel: Yenta: ISA IRQ mask 0x0cf8, PCI irq 169
Jul 6 09:41:47 kernel: Socket status: 30000006
Jul 6 09:41:48kernel: pcmcia: parent PCI bridge I/O window: 0x5000 - 0x5fff
Jul 6 09:41:48 kernel: cs: IO port probe 0x5000-0x5fff: clean.
Jul 6 09:41:48 kernel: pcmcia: parent PCI bridge Memory window: 0xc8200000 - 0xc82fffff
Jul 6 09:41:48 kernel: pcmcia: parent PCI bridge Memory window: 0x50000000 - 0x51ffffff
Jul 6 09:41:48 kernel: usbcore: registered new driver libusual
Jul 6 09:41:48 kernel: usbcore: registered new driver hiddev
Jul 6 09:41:48 kernel: usbcore: registered new driver usbhid
Jul 6 09:41:48 kernel: drivers/usb/input/hid-core.c: v2.6:USB HID core driver
Jul 6 09:41:48 kernel: PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSE0] at 0x60,0x64 irq 1,12
Jul 6 09:41:48 kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Jul 6 09:41:48 kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Jul 6 09:41:48 kernel: mice: PS/2 mouse device common for all mice
Jul 6 09:41:48 kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
Jul 6 09:41:49 kernel: md: bitmap version 4.39
Jul 6 09:41:49 kernel: TCP bic registered
Jul 6 09:41:49 kernel: Initializing IPsec netlink socket
Jul 6 09:41:49 kernel: NET: Registered protocol family 1
Jul 6 09:41:49 kernel: NET: Registered protocol family 17
Jul 6 09:41:49 kernel: Using IPI No-Shortcut mode
Jul 6 09:41:49 kernel: ACPI wakeup devices:
Jul 6 09:41:49 kernel: LAN KBC0 MSE0
Jul 6 09:41:49 kernel: ACPI: (supports S0 S3 S4 S5)
Jul 6 09:41:49 kernel: Freeing unused kernel memory: 244k freed
Jul 6 09:41:49 kernel: Write protecting the kernel read-only data: 723k
Jul 6 09:41:49 kernel: input: AT Translated Set 2 keyboard as /class/input/input0
Jul 6 09:41:49 kernel: device-mapper: 4.6.0-ioctl (2006-02-17) initialised: dm-devel@redhat.com
Jul 6 09:41:49 kernel: Synaptics Touchpad, model: 1, fw: 6.2, id: 0x80b1, caps: 0xa04713/0x20040a
Jul 6 09:41:49 kernel: kjournald starting. Commit interval 5 seconds
Jul 6 09:41:49 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jul 6 09:41:49 kernel: input: SynPS/2 Synaptics TouchPad as /class/input/input1
Jul 6 09:41:49 kernel: audit(1152178832.468:2): enforcing=1 old_enforcing=0 auid=4294967295
Jul 6 09:41:49 kernel: security: 3 users, 6 roles, 1417 types, 151 bools, 1 sens, 256 cats
Jul 6 09:41:49 kernel: security: 57 classes, 41080 rules
Jul 6 09:41:49 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 6 09:41:49 kernel: SELinux: Completing initialization.
Jul 6 09:41:49 NetworkManager: <information> Will activate wired connection 'eth0' because it now has a link.
Jul 6 09:41:49 kernel: SELinux: Setting up existing superblocks.
Jul 6 09:41:49 kernel: SELinux: initialized (dev dm-0, type ext3), uses xattr
Jul 6 09:41:49 kernel: SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
Jul 6 09:41:49 kernel: SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts
Jul 6 09:41:49 kernel: SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts
Jul 6 09:41:49 kernel: SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs
Jul 6 09:41:49 kernel: SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses genfs_contexts
---To be continued---

name_user
6th July 2006, 03:46 PM
Jul 6 09:41:49 kernel: SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses genfs_contexts
Jul 6 09:41:49 kernel: SELinux: initialized (dev devpts, type devpts), uses transition SIDs
Jul 6 09:41:49 kernel: SELinux: initialized (dev eventpollfs, type eventpollfs), uses genfs_contexts
Jul 6 09:41:49 kernel: SELinux: initialized (dev inotifyfs, type inotifyfs), uses genfs_contexts
Jul 6 09:41:49 kernel: SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
Jul 6 09:41:49 kernel: SELinux: initialized (dev futexfs, type futexfs), uses genfs_contexts
Jul 6 09:41:49 kernel: SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
Jul 6 09:41:49 kernel: SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
Jul 6 09:41:49 kernel: SELinux: initialized (dev cpuset, type cpuset), not configured for labeling
Jul 6 09:41:49 kernel: SELinux: initialized (dev proc, type proc), uses genfs_contexts
Jul 6 09:41:49 kernel: SELinux: initialized (dev bdev, type bdev), uses genfs_contexts
Jul 6 09:41:49 kernel: SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
Jul 6 09:41:49 kernel: SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
Jul 6 09:41:49 kernel: audit(1152178832.836:3): policy loaded auid=4294967295
Jul 6 09:41:49 kernel: SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts
Jul 6 09:41:49 kernel: hw_random: cannot enable RNG, aborting
Jul 6 09:41:49 kernel: 8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
Jul 6 09:41:49 kernel: 8139cp: pci dev 0000:0b:02.0 (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
Jul 6 09:41:49 kernel: 8139cp: Try the "8139too" driver instead.
Jul 6 09:41:49 kernel: 8139too Fast Ethernet driver 0.9.27
Jul 6 09:41:49 kernel: ACPI: PCI Interrupt 0000:0b:02.0[A] -> GSI 20 (level, low) -> IRQ 225
Jul 6 09:41:49 kernel: eth0: RealTek RTL8139 at 0xf8838400, 00:c0:9f:90:8b:f6, IRQ 225
Jul 6 09:41:49 kernel: sdhci: Secure Digital Host Controller Interface driver, 0.11
Jul 6 09:41:49 kernel: sdhci: Copyright(c) Pierre Ossman
Jul 6 09:41:49 kernel: PCI: Enabling device 0000:0b:00.4 (0000 -> 0002)
Jul 6 09:41:49 kernel: ACPI: PCI Interrupt 0000:0b:00.4[A] -> GSI 16 (level, low) -> IRQ 169
Jul 6 09:41:49 kernel: mmc0: SDHCI at 0xc8209000 irq 169 PIO
Jul 6 09:41:49 kernel: mmc1: SDHCI at 0xc8208c00 irq 169 PIO
Jul 6 09:41:49 kernel: mmc2: SDHCI at 0xc8208800 irq 169 PIO
Jul 6 09:41:49 kernel: ieee80211: 802.11 data/management/control stack, git-1.1.7
Jul 6 09:41:49 kernel: ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
Jul 6 09:41:49 kernel: bcm43xx driver
Jul 6 09:41:49 kernel: PCI: Enabling device 0000:0b:03.0 (0000 -> 0002)
Jul 6 09:41:49 kernel: ACPI: PCI Interrupt 0000:0b:03.0[A] -> GSI 17 (level, low) -> IRQ 177
Jul 6 09:41:49 kernel: bcm43xx: Chip ID 0x4306, rev 0x3
Jul 6 09:41:49 kernel: bcm43xx: Number of cores: 5
Jul 6 09:41:50 kernel: bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243, enabled
Jul 6 09:41:50 kernel: bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243, disabled
Jul 6 09:41:50 kernel: bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243, enabled
Jul 6 09:41:50 kernel: bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243, disabled
Jul 6 09:41:50 kernel: bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243, enabled
Jul 6 09:41:50 kernel: bcm43xx: PHY connected
Jul 6 09:41:50 kernel: bcm43xx: Detected PHY: Version: 2, Type 2, Revision 2
Jul 6 09:41:50 kernel: bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
Jul 6 09:41:50 kernel: bcm43xx: Radio turned off
---To be continued---

Firewing1
6th July 2006, 03:47 PM
Name_user, it's easier if you dump all that into a text file and then just attach it.
Firewing1

name_user
6th July 2006, 03:49 PM
Jul 6 09:41:50 kernel: ACPI: PCI Interrupt 0000:00:1e.2[A] -> GSI 22 (level, low) -> IRQ 209
Jul 6 09:41:50 kernel: intel8x0_measure_ac97_clock: measured 58069 usecs
Jul 6 09:41:50 kernel: intel8x0: clocking to 48000
Jul 6 09:41:50 kernel: ACPI: PCI Interrupt 0000:00:1e.3[A] -> GSI 22 (level, low) -> IRQ 209
Jul 6 09:41:50 kernel: MC'97 0 converters and GPIO not ready (0x1)
Jul 6 09:41:50 kernel: cs: IO port probe 0x100-0x3af: clean.
Jul 6 09:41:50 kernel: cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
Jul 6 09:41:50 kernel: cs: IO port probe 0x820-0x8ff: clean.
Jul 6 09:41:50 kernel: cs: IO port probe 0xc00-0xcf7: clean.
###Above is the whole session of starting up###

name_user
6th July 2006, 03:51 PM
Thanks for the reminding. I hope somebody here could identify some problem with my kernel. Thanks in advance.

Firewing1
6th July 2006, 04:00 PM
Try the new kernel - it should run better.
Firewing1

scotta3234
6th July 2006, 04:22 PM
Ahh new kernel just in time. 2139 just flat out didn't wanna load X. Now if i could only figure out how to make an 8.24 ati driver against the new kernel.

sentry
6th July 2006, 07:32 PM
Ahh new kernel just in time. 2139 just flat out didn't wanna load X. Now if i could only figure out how to make an 8.24 ati driver against the new kernel.

Livna has a build up already...

scotta3234
6th July 2006, 07:36 PM
They have an 8.26 driver for the new kernel but only the 8.24 ati driver works for my environment. I've wondered if there was a way i could use the old version of the driver with newer kernels. I have asked this question before in the post, "8.24 ati driver in with new kernel."

sentry
6th July 2006, 07:39 PM
They have an 8.26 driver for the new kernel but only the 8.24 ati driver works for my environment. I've wondered if there was a way i could use the old version of the driver with newer kernels. I have asked this question before in the post, "8.24 ati driver in with new kernel."
I see, that's unfortunate to hear :( I wish I could help with your issue.

name_user
8th July 2006, 03:56 PM
New kernel 2.6.17.2145 now seems working on my computer after ATI driver is updated. However, I see a line saying BIOS bug during starting up. There is wireless driver for broadcom, but I haven't figured it out how to make it work. That sounds a progress.

name=carlos
12th July 2006, 05:59 PM
I've had problems with this release; until now I've used 2.6.16 and it still works now; but this version doesn't make it to the login screen. It seems to complete startup fine (completes everything [ OK ] except for eth1, which I KNOW isn't attached, and this doesn't affect 2.6.16), then just goes to a blank, black screen and stays there.
The first few log entries for a start-up with this version are:

Jul 12 17:17:05 localhost syslogd 1.4.1: restart.
Jul 12 17:17:05 localhost kernel: klogd 1.4.1, log source = /proc/kmsg started.
Jul 12 17:17:05 localhost kernel: Linux version 2.6.17-1.2145_FC5 (brewbuilder@hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)) #1 Sat Jul 1 13:03:45 EDT 2006
The last are as follows:


Jul 12 17:17:14 localhost smartd[1776]: Monitoring 1 ATA and 0 SCSI devices
Jul 12 17:17:14 localhost smartd[1778]: smartd has fork()ed into background mode. New PID=1778.
Jul 12 17:17:15 localhost hpiod: 0.9.11 accepting connections at 50000...
Jul 12 17:17:17 localhost gpm[1857]: *** info [startup.c(95)]:
Jul 12 17:17:17 localhost gpm[1857]: Started gpm successfully. Entered daemon mode.
Jul 12 17:17:18 localhost avahi-daemon[1978]: Found user 'avahi' (UID 70) and group 'avahi' (GID 70).
Jul 12 17:17:18 localhost avahi-daemon[1978]: Successfully dropped root privileges.
Jul 12 17:17:18 localhost avahi-daemon[1978]: avahi-daemon 0.6.10 starting up.
Jul 12 17:17:19 localhost avahi-daemon[1978]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Jul 12 17:17:19 localhost avahi-daemon[1978]: Successfully called chroot().
Jul 12 17:17:19 localhost avahi-daemon[1978]: Successfully dropped remaining capabilities.
Jul 12 17:17:19 localhost avahi-daemon[1978]: No service found in /etc/avahi/services.
Jul 12 17:17:19 localhost avahi-daemon[1978]: Network interface enumeration completed.
Jul 12 17:17:19 localhost avahi-daemon[1978]: Registering HINFO record with values 'I686'/'LINUX'.
Jul 12 17:17:19 localhost avahi-daemon[1978]: Server startup complete. Host name is localhost.local. Local service cookie is 2668972504.
Jul 12 17:17:30 localhost kernel: [drm] Initialized drm 1.0.1 20051102
Then the log starts again at the next boot of the (functioning) 2.6.16 version.

Any ideas? I am genuinely clueless.