2.6 hoses 2.4 on old-world?

2.6 hoses 2.4 on old-world?

[Stefan Jeglinski]

Been running a 2.4 kernel on my PowerTowerPro for a long time. Over
the months I've tried building 2.6.x, and succeeded for the first
time last night with 2.6.8-rc1. Tried booting (via BootX of course),
but lost all video immediately (completely black on the console, thin
green pinstripes when I [blindly] start X).

Rebooted to the default 2.4 but I'm hosed: The first part of the boot
starts, and sometime shortly after I get to the yellow Welcome to
Yellowdog lettering, then I'm seeing a lot of "/dev/null, read-only
file system" messages, and I'm dropped (after a root password) in a
shell with the prompt

	(Repair filesystem) N #

where N starts at one and increases if I type certain things at the
prompt, like "ls."

/etc/mtab shows:

	/dev/sda6 / ext3 rw 0 0
	none /proc proc rw 0 0

But if I try e2fsck /dev/sda6, I get 'couldn't open /dev/null
(read-only file system)' despite what mtab says. I can't seem to
umount anything to try remounting.

I was running journaled in 2.4, and I might have forgotten to build
in ext3 support in 2.6 - did this hose my installation? It's been
such a long time since I had to fsck anything, am I forgetting
something simple?


Stefan Jeglinski


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.6 hoses 2.4 on old-world?

[CaT]

On Fri, Aug 20, 2004 at 09:04:23PM -0400, Stefan Jeglinski wrote:
> But if I try e2fsck /dev/sda6, I get 'couldn't open /dev/null
> (read-only file system)' despite what mtab says. I can't seem to
> umount anything to try remounting.

do an 'ls -l /dev/null'. Does it look something like this?

crw-rw-rw-  1 root root 1, 3 2004-08-14 04:37 /dev/null

If not then remove it and type

mknod /dev/null c 1 3

You'll need to mount the fs rw first though. This should do it:

mount -o 'remount,rw' /

And don't forget to remount ro when you're done.

--
    Red herrings strewn hither and yon.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.6 hoses 2.4 on old-world?

[Stefan Jeglinski]

>Been running a 2.4 kernel on my PowerTowerPro for a long time. Over
>the months I've tried building 2.6.x, and succeeded for the first
>time last night with 2.6.8-rc1.

sorry, that's rc4 I'm using.

>Rebooted to the default 2.4 but I'm hosed: The first part of the boot
>starts, and sometime shortly after I get to the yellow Welcome to
>Yellowdog lettering, then I'm seeing a lot of "/dev/null, read-only
>file system" messages,

The problem is that something overwrote /dev/null as a regular file,
and the errors leading to boot failure were of the type "bad file
descriptor."

I remounted rw, deleted /dev/null, and recreated it. I can now boot
back into 2.4.

Question remains - is there something about 2.6 on old-world systems?
Is is not safe? Unstable? (I still haven't figured out why I lose
video with 2.6).

Steps:

make menuconfig
(do some config)
make
make modules_install
reboot

I admit to being somewhat confused, this is cleaner but less
informative than the 2.4 build procedure.

BTW depmod give me lots of unresolved symbols, mostly related to sound.


Stefan Jeglinski

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.6 hoses 2.4 on old-world?

[Stefan Jeglinski]

>Steps:
>
>make menuconfig
>(do some config)
>make
>make modules_install
>reboot

Confirmed. Something about this procedure with 2.6.8-rc4 is hosing
/dev/null, and I have to delete it and mknod again. Is this a known
bug, or have I discovered something that everybody's known about
forever, and I should slink away. Or maybe I don't understand how to
build/install 2.6 correctly?

I hear YDL-4 won't support BootX - is this convenience or is
something now permanently broken for old-world and kernel 2.6?


Stefan Jeglinski

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.6 hoses 2.4 on old-world?

[Olaf Hering]

 On Fri, Aug 20, Stefan Jeglinski wrote:

>
> >Steps:
> >
> >make menuconfig
> >(do some config)
> >make
> >make modules_install
> >reboot
>
> Confirmed. Something about this procedure with 2.6.8-rc4 is hosing
> /dev/null, and I have to delete it and mknod again. Is this a known
> bug, or have I discovered something that everybody's known about
> forever, and I should slink away. Or maybe I don't understand how to
> build/install 2.6 correctly?

for starters:

useradd -m jeglin
su - jeglin
tar xfj linux-2.6.8.1.tar.bz2
cd linux-2.6.8.1
make menuconfig
make all
cd ~jeglin/linux-2.6.8.1
make modules_install
reboot

the binutils check (?) will remove /dev/null

--
USB is for mice, FireWire is for men!

sUse lINUX ag, nÜRNBERG

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.6 hoses 2.4 on old-world?

[Sam Ravnborg]

On Sun, Aug 22, 2004 at 12:51:18AM +0200, Olaf Hering wrote:
>
>  On Fri, Aug 20, Stefan Jeglinski wrote:
>
> >
> > >Steps:
> > >
> > >make menuconfig
> > >(do some config)
> > >make
> > >make modules_install
> > >reboot
> >
> > Confirmed. Something about this procedure with 2.6.8-rc4 is hosing
> > /dev/null, and I have to delete it and mknod again. Is this a known
> > bug, or have I discovered something that everybody's known about
> > forever, and I should slink away. Or maybe I don't understand how to
> > build/install 2.6 correctly?
>
> for starters:
>
> useradd -m jeglin
> su - jeglin
> tar xfj linux-2.6.8.1.tar.bz2
> cd linux-2.6.8.1
> make menuconfig
> make all
> cd ~jeglin/linux-2.6.8.1
> make modules_install
sudo make modules_install
> reboot
>
> the binutils check (?) will remove /dev/null

Yep - Tom Rini already notified me about this issue.
Problem is the way as handle output files.

Now I wonder why I do not see the problem here when executing the
culprint part of arch/ppc/Makefile manually:

sam@mars kbuild $ sudo ls -l /dev/null
crw-rw-rw-  1 root root 1, 3 Jun 15 23:54 /dev/null
sam@mars kbuild $ sudo echo dssall | as -many -o /dev/null >/dev/null 2>&1
sam@mars kbuild $ sudo ls -l /dev/null
crw-rw-rw-  1 root root 1, 3 Jun 15 23:54 /dev/null

Tom asked if we could use mktemp in the build process,
but I really do not know enough about potential security issues
to start doing this.
With mktemp we could avoid using /dev/null in the as check.

Another possibility was to parse the output of:
as --version | head -n 1 | cut -d ' ' -f 3
And then some sed/awk magic to fetch the three first numbers and
always make then two digits wide: 2.14.90.0.8 => 021490

	Sam

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: 2.6 hoses 2.4 on old-world?

[Stefan Jeglinski]

Olaf Hering:

>the binutils check (?) will remove /dev/null

Well, I found your earlier thread on binutils and the discussion of
the -many switch, but I'm not clear as to what this is all about. It
looks like my problem is two-fold:

1. To build 2.6.x, I need a newer binutils than my 2.13.90.0.18-6 (YDL 301)
2. The as check fails to tell me my binutils is too old (?)

Is this correct? Since I don't see the error, what version of
binutils do I need? Just the "latest?" Not having done so yet, will I
have to upgrade various other things as well? (gcc, etc).

Sam Ravnborg:

>Yep - Tom Rini already notified me about this issue.
>Problem is the way as handle output files.

I think this is the same thread I was talking about. What I'm really
unclear on is the "correct" way to handle this. It seems like the
discussion about changing AFLAGS is still alive? Also from the
earlier thread, it seems like maybe the latest binutils will not
necessarily fix the issue, as something has changed in binutils?

Sorry to be such a newbie on this. I'm obviously 2-3 months behind
the discussion, just now delving into 2.6...


Stefan Jeglinski

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/