You are not logged in.

#51 2005-12-17 15:28:05

ffderrick
Member
Registered: 2004-03-13
Posts: 11

Re: INITRD - share your woes

I just upgraded to the 2.6.14 kernel with initrd.
The kernel booted properly with hwdetect although slowly.

Has anyone noticed a slow down with everything.
apps load painfully slow now.
I use fluxbox and it's taking 8 seconds to fully load. (used to be 1)
firefox takes 40 seconds to load.

Solved:  It seems to have fixed itself after another -Syu and reboot.
Thanks


"I hate rude behavior in a man.  Won't tolerate it."

Offline

#52 2005-12-17 17:31:14

AndyRTR
Developer
From: Magdeburg/Germany
Registered: 2005-10-07
Posts: 1,637

Re: INITRD - share your woes

Check if DMA is activated.

Offline

#53 2005-12-17 17:32:32

depi
Member
From: EU - Slovakia
Registered: 2005-12-07
Posts: 39
Website

Re: INITRD - share your woes

Hi I have upgraded today the new kernel, intrd and others but I cant upgrade the nvidia package, how can I solve this problem? It tells me to shut down Xserver however the Xserver is shutted down and it writes that it cant find libGL or something that

Offline

#54 2005-12-17 17:36:38

AndyRTR
Developer
From: Magdeburg/Germany
Registered: 2005-10-07
Posts: 1,637

Re: INITRD - share your woes

There are other threads about the nvidia issue. The kernel has been  compiled with the wrong gcc. A new one will soon come out.

Offline

#55 2005-12-17 17:39:00

depi
Member
From: EU - Slovakia
Registered: 2005-12-07
Posts: 39
Website

Re: INITRD - share your woes

AndyRTR wrote:

There are other threads about the nvidia issue. The kernel has been  compiled with the wrong gcc. A new one will soon come out.

okay thanks very much!

Offline

#56 2005-12-17 17:49:55

jesus franco
Member
From: PA, USA
Registered: 2005-05-17
Posts: 66

Re: INITRD - share your woes

AndyRTR wrote:

There are other threads about the nvidia issue. The kernel has been  compiled with the wrong gcc. A new one will soon come out.

Ah, this must be why my ati driver can't compile either...
I guess the kernel is compiled with the gcc in testing? Am I right? GCC 4.1...

Aside from that the upgrade went perfectly here. no problems what so ever. After it was done automaticaly I used the wiki to customize it. big_smile removed cd/ide stuff off of the initrd.

EDIT:
Just did a check...the 2.6.14 in current is compiled with gcc 4.1.

[root@ArchLinux jesus]# cat /proc/version
Linux version 2.6.14-ARCH (root@earth) (gcc version 4.1.0 20051112 (experimental)) #1 SMP PREEMPT Wed Dec 7 15:10:15 PST 2005

Offline

#57 2005-12-17 18:37:26

apeiro
Daddy
From: Victoria, BC, Canada
Registered: 2002-08-12
Posts: 771
Website

Re: INITRD - share your woes

The latest kernel (2.6.14.4) is in Current now.  It was built with gcc 4.0, so nvidia will work again.

Offline

#58 2005-12-17 19:07:40

ozar
Member
From: USA
Registered: 2005-02-18
Posts: 1,681

Re: INITRD - share your woes

Just reporting my results with the new kernel/initrd thingy.  Hope it might help someone...  smile

I did my first install of the new 2.6.14(.4-1) stock kernel just now and it didn't go quite as easily as had been indicated, but it wasn't a huge burden getting rebooted, either.  The addition of initrd /initrd26.img to my menu.lst file wasn't enough, and I got the "error 15 : file not found" at reboot, but I quickly realized that /boot needed to be added to the path making the line read initrd /boot/initrd26.img.  I also got several hundred alsa errors on reboot, but running alsaconf fixed that.

There are a few other errors at boot I have yet to look into, but it'll probably all work out.  Internet is working.

The part that's a bit irritating and frankly kind of sucky is what I get when I run lsmod:

Module                  Size  Used by
uhci_hcd               31888  0 
ehci_hcd               33416  0 
usbhid                 48800  0 
usblp                  11904  0 
usb_storage            76864  0 
skge                   35344  0 
sk98lin               180704  0 
ppp_generic            27796  0 
slhc                    6656  1 ppp_generic
snd_emu10k1           121252  0 
snd_rawmidi            21152  1 snd_emu10k1
snd_ac97_codec         95484  1 snd_emu10k1
snd_ac97_bus            2176  1 snd_ac97_codec
snd_util_mem            3840  1 snd_emu10k1
snd_hwdep               7584  1 snd_emu10k1
snd_seq_oss            33408  0 
snd_seq_midi_event      6400  1 snd_seq_oss
snd_seq                52112  4 snd_seq_oss,snd_seq_midi_event
snd_seq_device          7436  4 snd_emu10k1,snd_rawmidi,snd_seq_oss,snd_seq
snd_pcm_oss            51104  0 
snd_pcm                84612  3 snd_emu10k1,snd_ac97_codec,snd_pcm_oss
snd_timer              22404  3 snd_emu10k1,snd_seq,snd_pcm
snd_page_alloc          8840  2 snd_emu10k1,snd_pcm
snd_mixer_oss          18048  1 snd_pcm_oss
snd                    49252  11 snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_hwdep,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
soundcore               8160  1 snd
nvidia               4083472  0 
shpchp                 96516  0 
pci_hotplug            26692  1 shpchp
parport_pc             26436  1 
serio_raw               6148  0 
pcspkr                  3688  0 
emu10k1_gp              3072  0 
gameport               12424  2 emu10k1_gp
evdev                   8064  0 
i2c_i801                8332  0 
i2c_core               18688  1 i2c_i801
tpm_nsc                 6016  0 
tpm_infineon            8336  0 
tpm_atmel               4992  0 
tpm                     8480  3 tpm_nsc,tpm_infineon,tpm_atmel
rtc                    10808  0 
ppdev                   7812  0 
lp                      9860  0 
hw_random               4756  0 
intel_agp              21532  1 
agpgart                30032  2 nvidia,intel_agp
usbcore               115584  6 uhci_hcd,ehci_hcd,usbhid,usblp,usb_storage
xfs                   562592  0 
reiserfs              270064  0 
jfs                   193148  0 
ext3                  133640  2 
jbd                    58132  1 ext3
sata_qstor              7556  0 
sata_promise            8836  0 
sata_nv                 7044  0 
sata_mv                 7300  0 
sata_vsc                5764  0 
sata_via                6276  0 
sata_uli                4864  0 
sata_svw                5764  0 
sata_sx4               12164  0 
sata_sis                5632  0 
sata_sil                6788  0 
mptfc                   5508  0 
mptspi                  6408  0 
mptsas                 11532  0 
mptctl                 23040  0 
mptscsih               33684  3 mptfc,mptspi,mptsas
mptbase                46048  5 mptfc,mptspi,mptsas,mptctl,mptscsih
megaraid_mbox          32528  0 
megaraid_sas           25644  0 
megaraid_mm            10020  1 megaraid_mbox
ata_piix                7684  0 
osst                   55072  0 
sym53c8xx              82452  0 
atp870u                30336  0 
aha152x                37584  0 
aic79xx               271960  0 
aic7xxx               182580  0 
ahci                    9988  0 
libata                 44936  13 sata_qstor,sata_promise,sata_nv,sata_mv,sata_vsc,sata_via,sata_uli,sata_svw,sata_sx4,sata_sis,sata_sil,ata_piix,ahci
raid_class              4224  0 
nsp32                  26132  0 
aacraid                56704  0 
ipr                    53024  0 
imm                    12040  0 
parport                33736  4 parport_pc,ppdev,lp,imm
3w_xxxx                27680  0 
tmscsim                21824  0 
dc395x                 36492  0 
3w_9xxx                32516  0 
a100u2w                10304  0 
BusLogic               24756  0 
sr_mod                 15652  0 
qlogicfas408            6792  0 
st                     39328  0 
sg                     31648  0 
dmx3191d               14080  0 
qla6312               115072  0 
qla2322               134144  0 
qla2300               124416  0 
qla2200                87168  0 
qla2100                79488  0 
qla2xxx               128220  5 qla6312,qla2322,qla2300,qla2200,qla2100
lpfc                  153660  0 
scsi_transport_sas     12928  1 mptsas
qla1280               119436  0 
sd_mod                 15488  0 
ide_floppy             18176  0 
ide_cd                 39812  0 
cdrom                  38688  2 sr_mod,ide_cd
ide_disk               16128  4 
via82cxxx              13468  0 [permanent]
trm290                  4228  0 [permanent]
triflex                 3456  0 [permanent]
slc90e66                5376  0 [permanent]
sis5513                15624  0 [permanent]
siimage                11264  0 [permanent]
serverworks             8840  0 [permanent]
sc1200                  6784  0 [permanent]
rz1000                  2560  0 [permanent]
piix                    9732  0 [permanent]
pdc202xx_old           10240  0 [permanent]
pdc202xx_new            8704  0 [permanent]
ns87415                 4040  0 [permanent]
it821x                  8196  0 [permanent]
hpt366                 18688  0 [permanent]
hpt34x                  4736  0 [permanent]
generic                 4356  0 [permanent]
cy82c693                4356  0 [permanent]
cs5530                  5120  0 [permanent]
cmd64x                 11164  0 [permanent]
atiixp                  5520  0 [permanent]
amd74xx                14364  0 [permanent]
alim15x3               11276  0 [permanent]
aec62xx                 6912  0 [permanent]
ide_core              119376  28 usb_storage,ide_floppy,ide_cd,ide_disk,via82cxxx,trm290,triflex,slc90e66,
sis5513,siimage,serverworks,sc1200,rz1000,piix,pdc202xx_old,pdc202xx_new,
ns87415,it821x,hpt366,hpt34x,generic,cy82c693,cs5530,cmd64x,atiixp,
amd74xx,alim15x3,aec62xx

YIKES!  That's too many modules to be bothered with having to blacklist them in rc.conf, and I really didn't want to take the time to compile a custom kernel.

Is there some way of fixing this and keeping it "simple" so that I can stay with   Arch's keep it simple philosophy?

Thanks in advance...   smile


oz

Offline

#59 2005-12-17 19:19:26

arooaroo
Member
From: London, UK
Registered: 2005-01-13
Posts: 1,268
Website

Re: INITRD - share your woes

@ozar: that is almost exactly the same experience as I went through today (didn't have the alsa issues). I missed the /boot too, and was also gobsmacked at all the modules reported by lsmod. wtf?!?

Offline

#60 2005-12-17 19:24:13

ozar
Member
From: USA
Registered: 2005-02-18
Posts: 1,681

Re: INITRD - share your woes

arooaroo wrote:

@ozar: that is almost exactly the same experience as I went through today (didn't have the alsa issues). I missed the /boot too, and was also gobsmacked at all the modules reported by lsmod. wft?!?

hehe... glad you are up and running, arooaroo!

Looks like we are gonna get hit with the initscripts upgrades again, too.  I just upgraded them and now another upgrade has been posted.  They are all the way up to x.x.x-17 already!    :shock:    smile


oz

Offline

#61 2005-12-17 19:30:24

arooaroo
Member
From: London, UK
Registered: 2005-01-13
Posts: 1,268
Website

Re: INITRD - share your woes

Indeed. The upgrade went quite smooth - I was slightly nervous. Every time I upgrade my kernel I always seem to run in to problems - especially with wireless. Thankfully, the main problem was my own stupidity from following Judd's instructions too literally (i.e., omitting the '/boot' because he doesn't have it in his grub config!)

Offline

#62 2005-12-17 20:00:29

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

Re: INITRD - share your woes

Set AUTODETECT to 1 in /etc/mkinitrd.conf, specify your filesystem modules, remove hardware support that isn't needed (e.g. SATA and SCSI if your mobo doesn't support them). Then run 'mkinitrd auto' again, and reboot.

(The changes to mkinitrd.conf will stay in effect the next time you upgrade the kernel too, so this is basically set-and-forget.)

Offline

#63 2005-12-17 20:13:50

apeiro
Daddy
From: Victoria, BC, Canada
Registered: 2002-08-12
Posts: 771
Website

Re: INITRD - share your woes

ozar wrote:

Looks like we are gonna get hit with the initscripts upgrades again, too.  I just upgraded them and now another upgrade has been posted.  They are all the way up to x.x.x-17 already!    :shock:    smile

Yea, the -17 is my fault.  I messed up on a utf8 fix.  Sorry.

Offline

#64 2005-12-17 20:19:47

Snowman
Developer/Forum Fellow
From: Montreal, Canada
Registered: 2004-08-20
Posts: 5,212

Re: INITRD - share your woes

ozar wrote:

YIKES!  That's too many modules to be bothered with having to blacklist them in rc.conf, and I really didn't want to take the time to compile a custom kernel.

Is there some way of fixing this and keeping it "simple" so that I can stay with   Arch's keep it simple philosophy?

Thanks in advance...   smile

Try customizing your initrd. http://wiki.archlinux.org/index.php/Initrd

Offline

#65 2005-12-17 20:20:18

arooaroo
Member
From: London, UK
Registered: 2005-01-13
Posts: 1,268
Website

Re: INITRD - share your woes

Good tip - I shall give that a whirl. I didn't think I'd need to customize the initrd because in the wiki it says:

Most users will not have to customize their Initrd. This is for the power tweakers or people that just like to break their systems so they have something to do. You know who you are.  ;-)

So I stopped reading at that point as I thought - heck, I really don't fancy breaking my 'puter this weekend. smile

Offline

#66 2005-12-17 22:02:28

ozar
Member
From: USA
Registered: 2005-02-18
Posts: 1,681

Re: INITRD - share your woes

Thanks, Gullible and Snowman... that helped to remove about half of the modules.  I'll play with it more over the weekend and get it down a little further.


oz

Offline

#67 2005-12-18 00:01:02

ozar
Member
From: USA
Registered: 2005-02-18
Posts: 1,681

Re: INITRD - share your woes

Ahh... I knew I should have waited a few days to upgrade to the initrd kernel.  Upgraded to the new 2.6.14.4-1 kernel just a few hours ago and now have noticed that kernel 2.6.14.4-2 has just been uploaded to the repos.

Someday, I'll learn...    tongue   smile


oz

Offline

#68 2005-12-18 00:15:44

Snowman
Developer/Forum Fellow
From: Montreal, Canada
Registered: 2004-08-20
Posts: 5,212

Re: INITRD - share your woes

ozar wrote:

Thanks, Gullible and Snowman... that helped to remove about half of the modules.  I'll play with it more over the weekend and get it down a little further.

If you use hwdetect, you'll probably also  need to use MOD_BLACKLIST to prevent some of them to load.

Offline

#69 2005-12-19 05:34:35

apeiro
Daddy
From: Victoria, BC, Canada
Registered: 2002-08-12
Posts: 771
Website

Re: INITRD - share your woes

Hi dire.

When you're stuck at the initrd busybox shell, type this:

# cat /proc/partitions

What's in there?  Also, what's in /proc/modules?

Offline

#70 2005-12-19 07:37:56

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

Re: INITRD - share your woes

I do not like being in reduced shell (a dark place) would be handy for something to help start system from there chroot or something ...(not tried it yet!)

More to the point is it possible to start Arch from reduced shell (kernel is loaded at that point!)

emm just me 2c


Mr Green

Offline

#71 2005-12-19 19:20:21

apeiro
Daddy
From: Victoria, BC, Canada
Registered: 2002-08-12
Posts: 771
Website

Re: INITRD - share your woes

dire wrote:

I added a bunch of modules to HOSTCONTROLLER_IDE in /etc/mkinitrd.conf - "ide ide-disk piix hpt366" (doublechecked HPT controller - not 34x, but 366). Only "empty" REMOVE_XX in mkinitrd.conf left are now IDE, DM and FS - but the full initrd contains those modules also, so I'm still clueless why it (full initrd) doesn't work.

Hmmm.  I have a server with a HPT366 controller in it too, and I was bitten by the ol' IDE controller mixup problem.

The hpt366 module was loading BEFORE the piix one, so the highpoint controller would grab the first two ide busses (ide0 and ide1) so it got to be hda-hdd.  When PIIX loaded, it grabbed the second two (ide2 and ide3) and so it got hde-hdh.

The problem is that my root was /dev/hda1, so the initrd was looking at the wrong IDE controller.  I had to force the order by setting HOSTCONTROLLER_IDE manually.  Here's the relevant excerpt:

REMOVE_IDE=
REMOVE_SCSI=1
REMOVE_SATA=1
REMOVE_CDROM=
REMOVE_USB=1
REMOVE_FW=1
REMOVE_RAID=1
REMOVE_DM=1
REMOVE_FS=
HOSTCONTROLLER_IDE="generic piix hpt366"
HOSTCONTROLLER_SCSI=
HOSTCONTROLLER_SATA=
HOSTCONTROLLER_USB=
FILESYSTEMS="ext3"

This doesn't look the same problem as yours though, since you already have your hpt366 module at the end of HOSTCONTROLLER_IDE, where it should be.

You said you've added the hpt366 module and friends to HOSTCONTROLLER and rebuilt the initrd?  When you boot up with your new initrd, what do you /proc/modules and /proc/partitions show now?

I'm trying to see if the order of ide devices is being mixed up somewhere.  This seems to be the most common (besides mis-configuration) culprit in these situations, especially when one has multiple IDE controllers.

Offline

#72 2005-12-19 21:28:34

apeiro
Daddy
From: Victoria, BC, Canada
Registered: 2002-08-12
Posts: 771
Website

Re: INITRD - share your woes

dire wrote:

/proc/partitions

major minor  #blocks  name

   3     0    4202415 hda
   3     1      31153 hda1
   3     2    4171230 hda2
  33     0   58615704 hde
  33     1      33263 hde1
  33     2     262584 hde2
  33     3   58319856 hde3

Odd, that looks correct, doesn't it?  You say /dev/hde3 is your real root?

And this still doesn't work?

Offline

#73 2005-12-20 00:13:33

Bysshe
Member
Registered: 2004-12-10
Posts: 268

Re: INITRD - share your woes

AUTODETECT=1 works fine with me.   Specifying modules, even better.  tongue   Thanks!

Offline

#74 2005-12-20 00:54:22

apeiro
Daddy
From: Victoria, BC, Canada
Registered: 2002-08-12
Posts: 771
Website

Re: INITRD - share your woes

dire wrote:

Sorry, while I was making the edit to my previous post, I apparently forgot to mention it started working after manually specifying the modules :oops:

Ah, good to know!

Offline

#75 2005-12-21 04:26:09

AndyRTR
Developer
From: Magdeburg/Germany
Registered: 2005-10-07
Posts: 1,637

Re: INITRD - share your woes

I´m having trouble with creating the initrd while installing a kernel package. I need to go with kernel 2.6.15rc6. Running arch64 using latest mkinitrd from arch32 current.

[root@workstation64 kernel26rc_64]# pacman -U kernel26-2.6.15-
kernel26-2.6.15-1.pkg.tar.gz  kernel26-2.6.15-2.pkg.tar.gz  kernel26-2.6.15-3.pkg.tar.gz
[root@workstation64 kernel26rc_64]# pacman -U kernel26-2.6.15-3.pkg.tar.gz
loading package data... done.
checking for file conflicts... done.
upgrading kernel26... done.
Checking Input...
    Making image for standard Arch kernel (2.6.15-ARCH)...
Setting up Parameters...
    /lib/modules/2.6.15-ARCH found
Creating Initial RAM Disk...
cp: Aufruf von stat für ,,/sbin/busybox" nicht möglich: Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
cat: /tmp/copiedmodules: Datei oder Verzeichnis nicht gefunden
Checking Input...
    Building full initrd for Arch standard kernel
      (includes all possible modules)
Setting up Parameters...
    /lib/modules/2.6.15-ARCH found
Creating Initial RAM Disk...
cp: Aufruf von stat für ,,/sbin/busybox" nicht möglich: Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
ln: Zugriff auf ,,busybox": Datei oder Verzeichnis nicht gefunden
cat: /tmp/copiedmodules: Datei oder Verzeichnis nicht gefunden
[root@workstation64 kernel26rc_64]# 

Two initrd files are beeing created but no real difference:

[root@workstation64 kernel26rc_64]# ls -l /boot/initrd*
-rw-r--r--  1 root root 270503 2005-12-21 06:05 /boot/initrd26-full.img
-rw-r--r--  1 root root 271250 2005-12-21 06:05 /boot/initrd26.img

So what´s wrong here? Should there really be a file called /sbin/busybox?

Offline

Board footer

Powered by FluxBB