Big trouble after updating kernel

oldsko0l · 04-03-2006, 03:06 PM

Hi!
I'm posting this here because nobody seems to be able to help me on dutch forums

I have updated my kernel with yum from 2.6.11.etc to 2.6.16.etc.(the newest I guess).
So I reboot my pc and I get the graphical menu of grub where I can choose between the 2 kernels, so I take the newest. after he does the "udev-thing" and fixing the hardware I get a blank screen with a X as a cursor (of my mouse) and then nothing works exept my mouse... I tryed CTRL+ALT+F2 (for non-graphical mode) and CTRL+ALT+F7 (for graphical mode) but nothing happens. in other words I can't do anything exept moving my mouse around.

-->http://www.linuxplanet.com/graphics/...ra_startup.png
this is the screen I should get in stead of the blank screen so actually it's is not yet my login manager where it goes wrong but this is screen I should normally get in stead of the blank screen.

when I boot from init 3 (non-graphical mode) everything works okay I can open my login manager

Code:

/usr/bin/gdm

I can open my X

Code:

startx

So I guess the problem could be 2 things (maybe more, but you tell me..

)

1.My login manager (gdm) doesn't start automatically (I don't know how to fix this)

2.Most probably --> The problem has to do with this screen that does not appear (I don't know the name of this screen) http://www.linuxplanet.com/graphics/...ra_startup.png

Can anyone help me please? I really need this

btw.-The old kernel still works (but I need the new one)
-Please try to make the explanation not to difficult
-I'm using fedora core 4 and I'm using fluxbox as gui

Sorry for my complicated explanation and my bad english, I did the best I could

Lenard · 04-03-2006, 05:28 PM

First the screen is the Red Hat Graphical Boot (rhgb) screen, it's pretty but not really needed. As a quick test remove it from the kernel line for the new kernel.

Just press any key when the grub splash screen is displayed. Select the new kernel boot choice and press the 'e' key. Select the line that starts with something like 'kernel /vmlinuz' and press the 'e' key again. Remove the rhgb portion and the extra space. When done press the 'Enter' key followed by the 'b' key.

If this works then you should check and see if any updates for gdm and/or rhgb are avaialable, if not then you might want to consider removing the rhgb package for now. From the console or xterm session as root;

rpm -e rhgb or yum remove rhgb

oldsko0l · 04-04-2006, 12:12 PM

hej tnx man!! I love you

only when I reboot the rhgb line is back so how do I delete it permantely? because it's really stupid to delete it everytime you boot..

tnx again!

Lenard · 04-04-2006, 02:31 PM

Did you not read the second part, as root from the console or xterm session type something like (to un-install the package);
rpm -e rhgb

or

yum remove rhgb

If that does not work then (still as root) using your choice of text editor edit the /boot/grub/grub.conf file and remove it permantely.

oldsko0l · 04-04-2006, 05:47 PM

ah yes stupid of me

I will do that

and maybe you can help me with this
on the new kernel I have no internet connection..

I don't think it's normal I have all this troubles with updating my kernel? maybe I did it the wrong way?
I just did

Code:

yum -y update kernel

I guess I had to update some other things as well? or is this the right way to update it?

Lenard · 04-04-2006, 06:01 PM

Internet Connection??? Well it would be helpful to know the hardware specifactions of your system; lspci -v

What is different from the old kernel and the new kernel?? Did you forget to, for example, re-compile ndiswrapper???

oldsko0l · 04-04-2006, 06:10 PM

00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge Subsystem: VIA Technologies, Inc.: Unknown device 0000
Flags: bus master, 66Mhz, medium devsel, latency 8
Memory at e0000000 (32-bit, prefetchable) [size=64M]
Capabilities: [80] AGP version 3.5
Capabilities: [c0] Power Management version 2

00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: dde00000-dfefffff
Prefetchable memory behind bridge: d5d00000-ddcfffff
Capabilities: [80] Power Management version 2

00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at e400 [size=32]
Capabilities: [80] Power Management version 2

00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at e800 [size=32]
Capabilities: [80] Power Management version 2

00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at ec00 [size=32]
Capabilities: [80] Power Management version 2

00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI])
Subsystem: VIA Technologies, Inc. USB 2.0
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at dfffff00 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2

00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
Subsystem: VIA Technologies, Inc.: Unknown device 0000
Flags: bus master, stepping, medium devsel, latency 0
Capabilities: [c0] Power Management version 2

00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: VIA Technologies, Inc. VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE
Flags: bus master, medium devsel, latency 32, IRQ 255
I/O ports at fc00 [size=16]
Capabilities: [c0] Power Management version 2

00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
Subsystem: Elitegroup Computer Systems: Unknown device a101
Flags: medium devsel, IRQ 5
I/O ports at e000 [size=256]
Capabilities: [c0] Power Management version 2

00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded Ethernet Controller on VT8235
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at dc00 [size=256]
Memory at dffffe00 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 2

01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video (rev 01) (prog-if 00 [VGA])
Subsystem: VIA Technologies, Inc.: Unknown device 0000
Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 11
Memory at d8000000 (32-bit, prefetchable) [size=64M]
Memory at de000000 (32-bit, non-prefetchable) [size=16M]
Expansion ROM at dfef0000 [disabled] [size=64K]
Capabilities: [60] Power Management version 2
Capabilities: [70] AGP version 2.0

that's the output of lspci -v

Quote:

Did you forget to, for example, re-compile ndiswrapper???

I did never compile it..so let alone I re-compiled it

is it necesairry?

Quote:

What is different from the old kernel and the new kernel

I don't know.. I just need it to update my whole system (depencies)

Lenard · 04-04-2006, 07:56 PM

Do not worry about the ndiswrapper compile or re-compile, if you have not used it in the past then you don't need it know. The ndiswrapper is wireless and other drivers that do not have Linux support.

Now your ethernet interface is;
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)

and should use the via-rhine.ko module. So check with the old kernel and new kernel;

cat /proc/modules | grep via-rhine

If present in the old kernel and not present in the new kernel try;
modprobe -v via-rhine

Also have a look at your /etc/modprobe.conf and maybe /etc/modprobe.d/modprobe.conf.dist files for something like;

alias eth0 via-rhine

Lastly check your /lib/modules/<kernel-version-number-here/kernel/drivers/net directory for the module. Compare the old and new kernel versions, is the module missing in the new???

oldsko0l · 04-04-2006, 08:14 PM

okay I'll do that, I'll let you know what the results are.
But can you tell me what causes all these problems? was it my way of updating it or something else? because I'm scared some other things won't work either..

best regards,
oldsko0l

Lenard · 04-04-2006, 09:58 PM

And how did you update the kernel??

I normally get the vanilla kernel source from kernel.org and build my own.

$ uname -a
Linux Aspire5000 2.6.16.1 #1 Tue Apr 4 20:20:58 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux

oldsko0l · 04-05-2006, 04:37 AM

I just did

Code:

yum -y update kernel

oldsko0l · 04-05-2006, 05:47 AM

there is a small difference in the two /proc/modules file but I don't think that is the problem

Code:

[oldsko0l@localhost ~]$ cat /proc/modules | grep via_rhine
via_rhine 24133 0 - Live 0xce86f000
mii 5697 1 via_rhine, Live 0xce854000
[oldsko0l@localhost ~]$ cat modules_in_old_kernel
via_rhine 28361 0 - Live 0xce864000
mii 5441 1 via_rhine, Live 0xce834000

modprobe.conf has in the 2 kernels alias eth0 via-rhine

and in the map /lib/modules/2.6.16-1.2069_FC4/kernel/drivers/net
the file via-rhine.ko is present in the 2 kernels!

...

Lenard · 04-05-2006, 07:06 AM

OK the module is available and loaded in both kernels.....

Now check the output from ifconfig, example;

Code:

$ ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 00:XX:XX:XX:XX:XX
          inet addr:192.168.1.8  Bcast:192.168.1.255  Mask:255.255.255.0

Are you seeing your assigned IP or DHCP acquired address??

Does /etc/resolv.conf change from the old kernel and the new kernel??

What happens when you ping your router??? what happens when you ping your system??

Check your logs (/var/log/messages) do you see something like(DHCP acquired IP address);

Code:

Apr  4 23:07:10 localhost dhclient: DHCPREQUEST on eth1 to 192.168.XX.XX port 67
Apr  4 23:07:10 localhost dhclient: DHCPACK from 192.168.XX.XX
Apr  4 23:07:10 localhost dhclient: bound to 192.168.XX.XX -- renewal in 10041 seconds.

You might want to review;

http://www.tldp.org/HOWTO/Cable-Modem/index.html

oldsko0l · 04-05-2006, 10:13 AM

output ifconfig eth0

Quote:

eth0 Link encap:Ethernet HWaddr 00:0D:87:FF:84:EF
inet addr:192.168.0.193 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20d:87ff:feff:84ef/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:596 (596.0 b) TX bytes:450 (450.0 b)
Interrupt:16 Base address:0x6e00

output resolv.conf

Quote:

; generated by /sbin/dhclient-script
search telenet.be
nameserver 195.130.131.2
nameserver 195.130.130.130

output resolv.conf from old kernel =

Quote:

; generated by /sbin/dhclient-script
search telenet.be
nameserver 195.130.131.2
nameserver 195.130.130.130

Code:

[root@localhost oldsko0l]# cat /var/log/messages | grep dhc
[root@localhost oldsko0l]#

the same happens when I do this on my old kernel..

Quote:

What happens when you ping your router??? what happens when you ping your system??

I don't know what this is and how to do it

Lenard · 04-05-2006, 10:31 AM

Your system; ping 192.168.0.193

Now your router if you have one;

netstart -r

Take the Gateway IP address (it should look similar to you current IP address)

If you cannot ping your routers IP address then use; service iptables stop
and try again. If you can now, then try getting on the Internet, if you can then fix your iptables (Network Manager) and trust your ethernet device(s).

Sample /etc/sysconfig/iptables entry;

-A RH-Firewall-1-INPUT -p 50 -j ACCEPT

And before I get much deeper into this, how do you coonect to the Inernet anyhow, dialup, DSL direct (PPPoE or whatever) or DSL modem<-->Router<--->Internal System(s) or??

What does your /etc/sysconfig/network-scripts/ifcfg-eth0 script look like??