You are not logged in.

#26 2005-10-31 22:46:38

Gullible Jones
Member
Registered: 2004-12-29
Posts: 4,863

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

Me neither, but if you're going to change your hardware... Still, I suppose making an initrd isn't as annoying as, say, recompiling your kernel.

(Still, why would you want to use the initrd to load hardware that you could load the modules for in rc.conf? It wouldn't provide any advantage in most cases.)

Offline

#27 2005-11-01 14:39:59

glad
Member
From: Norway
Registered: 2005-11-01
Posts: 103
Website

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

i updated my kernel yesterday and i added the initrd file to grubs config file but when i reboot my computer i come in to a shell cold busybox what is that?? what did i do wrong

Offline

#28 2005-11-01 14:48:43

Mr Green
Forum Fellow
From: U.K.
Registered: 2003-12-21
Posts: 5,750

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

It seems to me that when trying out a new kernel you should always have old one as backup ...

Either rename old or new kernel edit grub/lilo & then if something is wrong you can just boot back into old kernel to figure it out ..

my 2c

(Must get round to loading 2.6.14)


Mr Green

Offline

#29 2005-11-01 15:46:59

glad
Member
From: Norway
Registered: 2005-11-01
Posts: 103
Website

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

Mr Green wrote:

It seems to me that when trying out a new kernel you should always have old one as backup ...

Either rename old or new kernel edit grub/lilo & then if something is wrong you can just boot back into old kernel to figure it out ..

my 2c

(Must get round to loading 2.6.14)

i did but i cant figure out the problem with initrd and kernel 2.6.14

Offline

#30 2005-11-01 16:08:02

lilsirecho
Veteran
Registered: 2003-10-24
Posts: 5,000

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

Latest edit info in wiki for lilo:
===========================================================
If you use Lilo add this to /etc/lilo.conf
image=/boot/vmlinuz26
        label=Arch
        vga=791
        root=/dev/hda1
        initrd=/boot/initrd26.img
        read-only
==============================================================

I surnise this assumes your root is /dev/hda1 but may be otherwise.

Note that the wiki includes troubleshooting info that may help solve the problems reported in this forum.


Sign of the times: Navajo blanket..made in China
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Online

#31 2005-11-01 16:23:31

Mr Green
Forum Fellow
From: U.K.
Registered: 2003-12-21
Posts: 5,750

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

ok I have added <point to your root partition> the important line is the initrd


Mr Green

Offline

#32 2005-11-01 18:59:39

Mr Green
Forum Fellow
From: U.K.
Registered: 2003-12-21
Posts: 5,750

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

Emmm busybox thats nice  :? 

Renamed vmlinuz26 to vmlinuz26-init in PKGBUILD but pacman wiped over vmlinuz26  :?

Anyway I must have done something wrong so I'm back to good old 2.6.13[/code]


Mr Green

Offline

#33 2005-11-01 22:18:07

rayjgu3
Member
From: Chicago IL usa
Registered: 2004-07-04
Posts: 692

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

this is pretty cool
got a question before trying this
if i load appropriate mod for usb ie:

REMOVE_IDE=
REMOVE_SCSI=
REMOVE_SATA=
REMOVE_CDROM=
REMOVE_USB=
REMOVE_FW=
REMOVE_RAID=
REMOVE_CRYPT=
ADD_MODULE= "uhci_hcd ohci_hcd ehci_hcd usbcore"
REMOVE_MODULE=
HOSTCONTROLLER_IDE=
HOSTCONTROLLER_SCSI=
HOSTCONTROLLER_SATA=
HOSTCONTROLLER_USB= "/dev/sda1"
CRYPT_DEVICE=

then make appropriate changes to lilo & fstab via chroot
then put this hard drive in an external case plug it into usb
boot off usb would i then have my very own ARCH to take with me everywhere?
as opposed to using some live distro using a nesting technique

any thoughts

Offline

#34 2005-11-01 23:06:59

T-Dawg
Forum Fellow
From: Wilmington, NC
Registered: 2005-01-29
Posts: 2,734

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

The way I understand it, the top section with the REMOVE_* specifies which subsystem to remove from the kernel and still be able to mount the root filesystem. So if you wanted to boot from IDE and USB you could probably set the rest to 1 to remove them. The bottom section is where you can further define the controller to the top section -otherwise leaving it blank add all possible modules. The add modules is for everything in between.
check the wiki for more info.

Offline

#35 2005-11-02 14:42:37

Mr Green
Forum Fellow
From: U.K.
Registered: 2003-12-21
Posts: 5,750

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

NOTE: After editing mkinitrd.conf, run mkinitrd auto as root to rebuild your Initrd

Try again ... mine I got busybox first time I tried it


Mr Green

Offline

#36 2005-11-02 15:49:02

tpowa
Developer
From: Lauingen , Germany
Registered: 2004-04-05
Posts: 2,261

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

Hi
ok next kernel release, that calls a legacy option.
- modularized the filesystems (ext2 needs to be in kernel!)
updated mkinitrd:
ok improvements with this release:
- now it's possible to use the 0.7 rescue CD + chroot to regenerate initrd smile
- added legacy option that builds a initrd26-legacy.img that includes all
possible modules. (will be additionally called on kernel install)
- Modularized the filesystem modules, ext2 is needed in kernel the rest can be loaded by initrd. (added this in kernel 2.6.14-2)
- added more comments to mkinitrd.conf.
- added more verboose grub setup after mkinitrd was run.
a grub autmatic update script is in the tests atm. Stay tuned for more.
Me will not do much work now on
it, i have a test next week at uni that needs to be done.
greetings tpowa

Offline

#37 2005-11-02 18:22:12

Chestah
Member
From: Schoorl, The Netherlands
Registered: 2005-02-08
Posts: 16

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

woot my reiserfs warning is gone, it's replacced by this one: EXT2-FS: blah fill blah : mounting EXT3 filesystem as EXT2

Offline

#38 2005-11-02 19:49:21

Moo-Crumpus
Member
From: Hessen / Germany
Registered: 2003-12-01
Posts: 1,442

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

Worked well with scsi and sata and jfs driven discs. Congratulations.


Frumpus addict
[mu'.krum.pus], [frum.pus]

Offline

#39 2005-11-02 21:08:55

lilsirecho
Veteran
Registered: 2003-10-24
Posts: 5,000

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

rayjgu3;

Don't forget the i686 needs for arch or the internet connection required.

Not "anywhere", but some of the USB interfaces may be useful on some computers.


Sign of the times: Navajo blanket..made in China
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Online

#40 2005-11-03 01:45:02

judland
Member
From: Sask., Canada
Registered: 2005-10-24
Posts: 55
Website

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

Okay... my turn.

I followed the Wiki, regarding the setup of initrd and I still get shunted to the BusyBox prompt.  The message I get, just before the # prompt is

/bin/sh: can't access tty; job control turned off

Now, I'm willing to call it 1for initrd, 0 for me and go back to the old kernel, but I'm not getting the results that the Wiki is telling me.

When i try to do pacman -S current/kernel26, I can't seem to get a connection to any of the mirrors to download the old kernel.  Do I have to manually set up some network configuration or something that the Wiki isn't telling me?

Offline

#41 2005-11-03 01:49:24

judland
Member
From: Sask., Canada
Registered: 2005-10-24
Posts: 55
Website

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

Oh, and I don't know if this means anything, but just before the BusyBox message appears, I see what appears to be an error code stating:

SGI XFS with ACLs, security atributes, large block numbers, no debug enabled

Offline

#42 2005-11-03 02:25:11

kakabaratruskia
Member
From: Santiago, Chile
Registered: 2003-08-24
Posts: 596

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

judland wrote:

Okay... my turn.

I followed the Wiki, regarding the setup of initrd and I still get shunted to the BusyBox prompt.  The message I get, just before the # prompt is

/bin/sh: can't access tty; job control turned off

Now, I'm willing to call it 1for initrd, 0 for me and go back to the old kernel, but I'm not getting the results that the Wiki is telling me.

When i try to do pacman -S current/kernel26, I can't seem to get a connection to any of the mirrors to download the old kernel.  Do I have to manually set up some network configuration or something that the Wiki isn't telling me?

I have the same problem here... I think it has to do with the new mkinitrd pkg. The last one worked fine.


And where were all the sportsmen who always pulled you though?
They're all resting down in Cornwall
writing up their memoirs for a paper-back edition
of the Boy Scout Manual.

Offline

#43 2005-11-03 02:39:19

judland
Member
From: Sask., Canada
Registered: 2005-10-24
Posts: 55
Website

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

kakabaratruskia wrote:

I have the same problem here... I think it has to do with the new mkinitrd pkg. The last one worked fine.

Hmmm... well, misery loves company, hey?  smile

Was able to get the old kernel back with the help of my Kanotix Live CD at least.  I'll stick with it until forced to change when the new kernel reaches /current.

Offline

#44 2005-11-03 03:12:16

normc
Member
From: Ottawa, Canada
Registered: 2004-06-28
Posts: 277
Website

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

I just installed the -14 from testing and followed the wiki to the letter.
On reboot everythink worked fine, KDE started and my icons on the desktop weren't scrambled for a change.


Norm

Offline

#45 2005-11-03 05:05:03

tpowa
Developer
From: Lauingen , Germany
Registered: 2004-04-05
Posts: 2,261

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

The mkinitrd-4 packages fixes the problem with the rootfs filesystem detection, the VFS problems should be gone now.
greetings
tpowa

Offline

#46 2005-11-03 09:37:50

sweiss
Member
Registered: 2004-02-16
Posts: 635

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

A little question about mkinitrd.conf: If I only want to load only ext3 and reiserfs, do I need to set REMOVE_FS=1 and FILESYSTEMS=ext3 reiserfs?

I've only set the FILESYSTEMS var and I also have xfs and jfs loaded as modules.

Offline

#47 2005-11-03 09:43:43

swiergot
Member
From: Kraków, Poland
Registered: 2005-01-08
Posts: 145

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

No, do NOT set REMOVE_FS to 1. But it's strange you get all the modules loaded. Maybe try to use quotation marks:

FILESYSTEMS="ext3 reiserfs"

Offline

#48 2005-11-03 10:45:07

tpowa
Developer
From: Lauingen , Germany
Registered: 2004-04-05
Posts: 2,261

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

yes the syntax is with "", without i don't know what happens.

oh and please rerun mkinitrd auto, mkinitrd legacy after mkinitrd upgrade to -4.
thanks

Offline

#49 2005-11-03 11:39:59

sweiss
Member
Registered: 2004-02-16
Posts: 635

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

I added the quotes and reran `mkinitrd auto`, works well now.

Thanks a lot for the help.

Offline

#50 2005-11-03 13:32:40

orjanp
Member
From: Tromsoe, Norway
Registered: 2004-07-03
Posts: 337

Re: [kernel] 2.6.14 : IMPORTANT CHANGES - upgraders please read

judland wrote:

Okay... my turn.

I followed the Wiki, regarding the setup of initrd and I still get shunted to the BusyBox prompt.  The message I get, just before the # prompt is

/bin/sh: can't access tty; job control turned off

Is there a way to fix this?

Orjanp


Ørjan Pettersen

Offline

Board footer

Powered by FluxBB