You are not logged in.
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
This is for kernel26.img. I successfully manually created kernel26-fallback.img according to kernel.install from kernel26. Not sure if anyone is having this problem.
Offline
Hmmm... can you post the output of "mkinitcpio -M" ?
Offline
Not sure what that was about but it is working now. Something required a reboot?. Thanks for responding phrakture. In case you're interested:
[root@mmccaskill600m mmccaskill]# mkinitcpio -k 2.6.18-ARCH -g /boot/kernel26.img -M
Modules autodetected:
cdrom
ide-cd
ide-core
ide-disk
generic
piix
b44
mii
ipw2200
pcmcia_core
rsrc_nonstatic
yenta_socket
usbcore
ehci-hcd
uhci-hcd
ieee80211_crypt
jbd
ext3
Offline
:: Begin build :: Parsing hook [base] :: Parsing hook [udev] :: Parsing hook [autodetect]
This is for kernel26.img. I successfully manually created kernel26-fallback.img according to kernel.install from kernel26. Not sure if anyone is having this problem.
Same here today for me. Unfortunately I posted a new thread on this without seeing this one.
Offline
Deleted the old thread.... let me look into this.
Offline
Ok, a few things:
1) Can you make sure it is hanging, and not just taking a really long time? (let it run for like 10 minutes)
2) What does "find /dev -type b" output?
3) Also, the output of "for b in $(find /dev -type b); do echo $b; done" ?
Offline
Ok, a few things:
1) Can you make sure it is hanging, and not just taking a really long time? (let it run for like 10 minutes)
2) What does "find /dev -type b" output?
3) Also, the output of "for b in $(find /dev -type b); do echo $b; done" ?
1. Done. After 20 minutes, still the same problem.
2. While 'Parsing hook [autodetect]' is still on the screen and I have not hit ctrl-c yet, I get this for output in step 2:
/dev/.tmp-8-66
/dev/.tmp-8-65
/dev/.tmp-8-50
/dev/.tmp-8-49
/dev/.tmp-8-34
/dev/.tmp-8-33
/dev/.tmp-8-18
/dev/.tmp-8-17
/dev/sda
/dev/.tmp-8-32
/dev/.tmp-8-16
/dev/.tmp-8-64
/dev/.tmp-8-48
/dev/hda10
/dev/hda9
/dev/hda11
/dev/hda13
/dev/hda8
/dev/hda7
/dev/hda6
/dev/hda5
/dev/hdb2
/dev/hda3
/dev/hda2
/dev/hda1
/dev/hdb1
/dev/hda12
/dev/hda
/dev/hdb
/dev/hdd
/dev/rd/9
/dev/rd/8
/dev/rd/7
/dev/rd/6
/dev/rd/5
/dev/rd/4
/dev/rd/3
/dev/rd/2
/dev/rd/15
/dev/rd/14
/dev/rd/13
/dev/rd/12
/dev/rd/11
/dev/rd/10
/dev/rd/1
/dev/rd/0
/dev/loop/7
/dev/loop/6
/dev/loop/5
/dev/loop/4
/dev/loop/3
3. While 'Parsing hook [autodetect]' is still on the screen and I have not hit ctrl-c yet, I get this for output in step 3:
bash: syntax error near unexpected token `do'
Offline
Interesting... do you have read permission on all these nodes? Can you delete those .tmp nodes?
Also, try upgrading to the newest mkinitcpio and trying that - it may change/fix the issue.
Offline
Interesting... do you have read permission on all these nodes? Can you delete those .tmp nodes?
Also, try upgrading to the newest mkinitcpio and trying that - it may change/fix the issue.
All of those .tmp nodes were created on this morning's boot, according to their time stamps. I couldn't delete them as root. And mkinitcpio is already current. On a hunch I just rebooted to see if those .tmp nodes reappeared. They did not. Now, doing
pacman -S kernel26
to reinstall goes to completion.
Offline
Following up ...
Actually, I now see that those .tmp nodes reappeared after reinstalling kernel26 with pacman.
Offline
Following up ...
Actually, I now see that those .tmp nodes reappeared after reinstalling kernel26 with pacman.
Just to see what would happen, I tried reinstalling kernel26 again, now that I see those .tmp nodes again, and the same problem arise. So those .tmp nodes are the problem. I'll reboot now and fix this with another kernel26 reinstallation.
Offline