Kernel update, b0rken system.....!

English Hardware
1

Has anyone noticed that the latest 64bit kernel from update is seriously
missing a few things?

Especially the main bootscreen and a shed load of other modules, this means
that the grub boot screen does not show and therefore no choice of O/S`s
infact no choice whatsoever, then the terminal is not the right vga size so
I cannot see most of the stuff.

And still my network does not start on boot, worked fine until about a month
ago then stopped being started during boot. This is a PC with static address
with ifup and onboot set.

I have got the module to load with the kernel:

<6>r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
<6>vendor=1002 device=597f
<6>r8169 0000:02:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
<7>r8169 0000:02:00.0: setting latency timer to 64
<6>eth0: RTL8168b/8111b at 0xffffc20000648000, 00:1f:d0:db:2f:b0, XID
38000000 IRQ 4349

I have it set in yast to boot with the system, dmesg shows:

Setting up (localfs) network interfaces:
lo
lo IP address: 127.0.0.1/8
IP address: 127.0.0.2/8
lo
doneWaiting for mandatory devices: eth0 NSC
0
eth0 device: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI
Express Gigabit Ethernet controller (rev 01)
eth0 is down
eth0
failed eth0 interface could not be set up until now
failedSetting up service (localfs) network . . . . . . . . .
…failed

What is the added NSC to the eth0?

During boot the lights on my switch show that there is activity but still no
network until I get to the desktop or a terminal and type rcnetwork restart.

I have even put that command in boot.local and still nothing.

But the main thing is what has happened to the bootscreen:

I hope this is just MY system otherwise there is going to be one big stink
in the groups later tonight.

But I cannot see what has happened yet, will report if I find anything out.

–
Mark

Nullus in verba
Nil illegitimi carborundum

2

baskitcaise adjusted his/her AFDB on Tuesday 09 Jun 2009 17:07 to write:

> But the main thing is what has happened to the bootscreen:
>
> I hope this is just MY system otherwise there is going to be one big stink
> in the groups later tonight.
>
> But I cannot see what has happened yet, will report if I find anything
> out.
>
>
>

Well after I kicked the cat* and muttered some choice words I fixed it (
simples )

I checked that the grub menu.lst was OK and noticed that it had lost my
settings for the vga= and and the kernel deadline option so I used Yast to
rewrite the list.

Then I just ran mkinitrd as root and reboot.

All is well again except that I still cannot get the ****ing network to
start at boot, I have enabled net boot rom inbios plugged the cable in and
out more times than I can think of but it still fails to initialise during
boot.

I wish I knew when this happened but as I seldom reboot I don`y know exactly
when this stopped working, the only thing I can relate to doing about the
time it stopped working was install virtualbox ver 22 from the virtualbox
site.

I have uninstalled that a while ago and still the prob exists.

I have just installed the latest 24ver thinking it might work a miracle but
nada, zip, nothing.

Anyone?

Cheers.

–
Mark

Nullus in verba
Nil illegitimi carborundum

3

Have you tried removing the network-config in Yast? If not, do so. Remove the network card, reboot and everything should be fully automatic, i.e. DHCP configured.
You don’t want the net boot option in BIOS on if you don’t use it. And you don’t.

Have you tried another network card? Network cards hardly ever break down, but yet they do. If another networkcard gives you the same trouble, you know it’s in the configuration.
Can you post the output of:
rcnetwork restart

If anything will work these days on linux it’s wired network cards.

4

Knurpht adjusted his/her AFDB on Wednesday 10 Jun 2009 11:36 to write:

>
> Have you tried removing the network-config in Yast?

Yes, tried with and without DHCP.

> If not, do so.
> Remove the network card, reboot and everything should be fully
> automatic, i.e. DHCP configured.

But this link is static and is defined in the router and switch for the
machines MAC address and has never changed since day 1, all machines here
have a static address.

> You don’t want the net boot option in BIOS on if you don’t use it. And
> you don’t.

Yeah I know I was just grasping at straws there :slight_smile:

>
> Have you tried another network card?

No but if I can get into my spares box and find a good enough one I will do
that

> Network cards hardly ever break
> down, but yet they do.

Well this is onboard and does work fine in “other O/S`s” ( spit ) and
Linuxes. ( What is the collective noun for Linux? ) :slight_smile:

> If another networkcard gives you the same
> trouble, you know it’s in the configuration.
> Can you post the output of:
> rcnetwork restart
>
> If anything will work these days on linux it’s wired network cards.
>
>

Yep I know, I am still leaning to the installation of virtualbox though as
it was about that time that it stopped starting on boot I wonder if the
vboxnet virtual adaptor might have changed the setup.

Now that I have more time I will have a search for it, was just in rant
mode yesterday after the broken kernel update luckily I knew the prob and
know how to fix things like that but the poor noobs will just freak.

As I said it was more an inconvenience to me as this machine is hardly ever
shutdown or rebooted.

If I find anything I will repost with a better subject.

Thanks.

–
Mark

Nullus in verba
Nil illegitimi carborundum

5

Collective name is linuces. :wink:

6

Knurpht adjusted his/her AFDB on Wednesday 10 Jun 2009 19:26 to write:

>
> Collective name is linuces. :wink:
>
>

ACK!

–
Mark

Nullus in verba
Nil illegitimi carborundum

7

On Wed June 10 2009 01:26 pm, Knurpht wrote:

>
> Collective name is linuces. :wink:
>
>
Maybe Lini. Is there not one Linux with multiple distributions and releases?

P. V.
“We’re all in this together, I’m pulling for you.” Red Green

8

PV adjusted his/her AFDB on Thursday 11 Jun 2009 05:30 to write:

> Maybe Lini. Is there not one Linux with multiple distributions and
> releases?

Well in that case if we go the penquin route, a baby penquin is a chick and
there are a choice of collective nouns:

colony of penguins
crèche of penguins
huddle of penguins
parcel of penguins
rookery of penguins

Take your pick.

:slight_smile:

Maybe going a bit too far OT here, might start a new thread in chit chat.

–
Mark

Nullus in verba
Nil illegitimi carborundum

9

To close this discussion:
It is one Linux, two Tuxes. Everybody OK ?

And it’s two Gnomæ , three KDEïş. That way we can show off our character composing talents as well.

10

For those with non-functioning sound as a result of the new 2.6.27.23 kernel, the SuSE-GmbH packager has now released the rpms for the update to 1.0.20 of alsa for the 2.6.27.23 kernel. Note this is on a special multimedia repository and not on the standard “update” repository.

There is guidance here for doing the update:
Alsa-update - openSUSE

Note one MUST send six zypper commands, being certain to pick the one’s specific to one’s openSUSE version. I recommend one optimize the alsa apps to be installed to match what one has on one’s PC already. … and also the second last command in the 3 command group should be specific to one’s kernel. Do NOT install multiple alsa-driver-kmp-<packages> … Only install the ONE that is applicable.

11

On Tue, 09 Jun 2009 16:54:00 GMT, baskitcaise <baskitcaise@gmx.co.uk>
wrote:

>baskitcaise adjusted his/her AFDB on Tuesday 09 Jun 2009 17:07 to write:
>
>> But the main thing is what has happened to the bootscreen:
>>
>> I hope this is just MY system otherwise there is going to be one big stink
>> in the groups later tonight.
>>
>> But I cannot see what has happened yet, will report if I find anything
>> out.
>>
>>
>>
>
>Well after I kicked the cat* and muttered some choice words I fixed it (
>simples )
>
>I checked that the grub menu.lst was OK and noticed that it had lost my
>settings for the vga= and and the kernel deadline option so I used Yast to
>rewrite the list.
>
>Then I just ran mkinitrd as root and reboot.
>
>All is well again except that I still cannot get the ****ing network to
>start at boot, I have enabled net boot rom inbios plugged the cable in and
>out more times than I can think of but it still fails to initialise during
>boot.
>
>I wish I knew when this happened but as I seldom reboot I don`y know exactly
>when this stopped working, the only thing I can relate to doing about the
>time it stopped working was install virtualbox ver 22 from the virtualbox
>site.
>
>I have uninstalled that a while ago and still the prob exists.
>
>I have just installed the latest 24ver thinking it might work a miracle but
>nada, zip, nothing.
>
>
>
>Anyone?
>
>Cheers.

I thought i had heard somewhere that if you have a kernel update you
have to reinstall/rebuild virtualization SW like VMware or VirtualBox
or whatever. If that is even relevant to your situation.