Re: Installing new kernel 2.6.17 on Ultra5
See if you can pass the boot options manually, as in from the command line
when you boot up the kernel, and I am not sure if you have to specify the
filesystem type, but I would look into that just in case. Also what file
system does you run, make sure the module for it is being loaded, and that
it's not something weird like that..
--Roman
PS: We really need to start working for better sparc support if we want to
keep it alive.
On Tue, Sep 19, 2006, John wrote:
> I finally gave up trying to compile my own kernel and decided to take
> Roman's advice.
>
> This certainly got me a little further.
>
> VFS: Cannot open boot device hda1 or unknown-block (0,0)
> Please append a correct "root=" in boot option.
> Kernel panic - not syncing etc....
>
> If you recall at the start of this thread I put the contents of
> silo.confwhich has:
>
> root=/dev/hda1 already stated.
>
> and my fstab (see above) hasn't changed.
>
> my / has:
> lrwxrwxrwx 1 root root 32 Sep 19 12:48 initrd.img -> boot/initrd.img-
> 2.6.17-2-sparc64
> lrwxrwxrwx 1 root root 29 Sep 19 12:48 vmlinuz -> boot/vmlinuz-
> 2.6.17-2-sparc64
>
> and my /boot has:
>
> -rw-r--r-- 1 root root 837342 Sep 1 04:15 System.map-2.6.17-2-sparc64
> lrwxrwxrwx 1 root root 1 Jul 26 2005 boot -> .
> -rw-r--r-- 1 root root 40131 Aug 31 21:57 config-2.6.17-2-sparc64
> lrwxrwxrwx 1 root root 1 Jul 26 2005 etc -> .
> -rw-r--r-- 1 root root 1024 Jun 21 12:57 fd.b
> -rw-r--r-- 1 root root 512 Jun 21 12:57 first.b
> -rw-r--r-- 1 root root 1024 Jun 21 12:57 generic.b
> -rw-r--r-- 1 root root 692 Jun 21 12:57 ieee32.b
> -rw-r--r-- 1 root root 4478995 Sep 19 12:48 initrd.img-2.6.17-2-sparc64
> -rw-r--r-- 1 root root 6928 Jun 21 12:57 isofs.b
> -rw-r--r-- 1 root root 7680 May 28 2005 old.b
> -rw-r--r-- 1 root root 62976 Jul 28 09:45 second.b
> -rw-r--r-- 1 root root 77 Sep 19 12:06 silo.conf
> -rw-r--r-- 1 root root 60829 Jun 21 12:57 silotftp.b
> -rw-r--r-- 1 root root 512 Jun 21 12:57 ultra.b
> -rw-r--r-- 1 root root 1379575 May 28 2005 vmlinuz-2.4.18-sun4u
> -rw-r--r-- 1 root root 1442770 Sep 1 04:15 vmlinuz-2.6.17-2-sparc64
>
> I've also tried:
>
> image=/vmlinuz-2.6.17...........
> label=linux
> initrd=/initrd-2.6.17.........
>
> and
>
> image=1/vmlinuz-2.6.17...........
> label=linux
> initrd=1/initrd-2.6.17.........
>
> but that didn't even find the image and left me in bootp.
>
> I think I'm so close I can smell it but I still need a helping hand, please.
>
> John
>
> On 9/15/06, Roman Shakin <rshakin@unixfreak.org> wrote:
> >
> >www.backports.com read it do it... also why exactly are you upgrading the
> >kernel ? 2.4 is alot more stable for sparc atleast... I have a ultra 5 and
> >I've had issues with 2.6 version kernels. backports have the 2.6 testing
> >kernel on them somewhere you will be able to upgrade it using aptitude or
> >apt
> >
> >
> >--Roman
> >
> >On Fri, Sep 15, 2006, John wrote:
> >
> >> Can you point me in the right direction/url, Roman?
> >>
> >>
> >> On 9/15/06, Roman Shakin <rshakin@unixfreak.org> wrote:
> >> >
> >> >Why dont you try using the backports package, i've tried compiling the
> >> >kernel
> >> >before and it has not worked, but my problem was with Adaptec drivers.
> >> >
> >> >--Roman
> >> >
> >> >On Fri, Sep 15, 2006, John wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> I have just compiled a new kernel for my Ultra5 using Debian's
> >> >> kernel-package system.
> >> >>
> >> >> BootP gets to the point of 'Booting into Linux...' and stops. No
> >error
> >> >> message nothing, just halts where it is! If I change vmlinuz to point
> >at
> >> >the
> >> >> old kernel it works fine.
> >> >>
> >> >> I'm obviously missing something but what?
> >> >>
> >> >> My / links are:
> >> >> lrwxrwxrwx 1 root root 25 May 28 2005 vmlinuz.old ->
> >> >boot/vmlinuz-
> >> >> 2.4.18-sun4u
> >> >> lrwxrwxrwx 1 root root 32 Sep 14 15:39 vmlinuz ->
> >boot/vmlinuz-
> >> >> 2.6.17.060914-sun4u
> >> >>
> >> >> My silo.conf is:
> >> >> partition=1
> >> >> root=/dev/hda1
> >> >> timeout=100
> >> >> image=1/vmlinuz
> >> >> label=linux
> >> >> read-only
> >> >>
> >> >> My /boot is:
> >> >> -rw-r--r-- 1 root root 848101 Sep 14 15:23
> >> >System.map-2.6.17.060914-sun4u
> >> >> lrwxrwxrwx 1 root root 1 Jul 26 2005 boot -> .
> >> >> -rw-r--r-- 1 root root 29349 Sep 14 14:08
> >config-2.6.17.060914-sun4u
> >> >> lrwxrwxrwx 1 root root 1 Jul 26 2005 etc -> .
> >> >> -rw-r--r-- 1 root root 1024 Jun 21 12:57 fd.b
> >> >> -rw-r--r-- 1 root root 512 Jun 21 12:57 first.b
> >> >> -rw-r--r-- 1 root root 1024 Jun 21 12:57 generic.b
> >> >> -rw-r--r-- 1 root root 692 Jun 21 12:57 ieee32.b
> >> >> -rw-r--r-- 1 root root 6928 Jun 21 12:57 isofs.b
> >> >> -rw-r--r-- 1 root root 7680 May 28 2005 old.b
> >> >> -rw-r--r-- 1 root root 62976 Jul 28 09:45 second.b
> >> >> -rw-r--r-- 1 root root 78 Feb 2 2006 silo.conf
> >> >> -rw-r--r-- 1 root root 60829 Jun 21 12:57 silotftp.b
> >> >> -rw-r--r-- 1 root root 512 Jun 21 12:57 ultra.b
> >> >> -rw-r--r-- 1 root root 1379575 May 28 2005 vmlinuz-2.4.18-sun4u
> >> >> -rw-r--r-- 1 root root 1452906 Sep 14 15:23
> >vmlinuz-2.6.17.060914-sun4u
> >> >>
> >> >> and /etc/fstab is:
> >> >> /dev/hda1 / ext3 errors=remount-ro 0
> >> >1
> >> >> /dev/hda2 none swap sw 0
> >> >0
> >> >> proc /proc proc defaults 0
> >> >0
> >> >> /dev/fd0 /floppy auto user,noauto 0
> >> >0
> >> >> /dev/cdrom /cdrom iso9660 ro,user,noauto 0
> >> >0
> >> >>
> >> >> If you need any other info to help, please let me know.
> >> >>
> >> >> TIA
> >> >>
> >> >> John
> >> >
> >
Reply to: