You are not logged in.
Have got arch32 & arch64 running on separate partitions on an Asrock Dual Sata mobo.
main HDD is a SataII, plugged to the SataII connector.
2nd HDD is a IDE Maxtor dedicated for backups plugged to the IDE connector.
Updated arch32 to latest kernel-2.6.19 with confidence it'll work, as it has not intel i.e. no piix here (News #229). But it doesn't boot anymore :-(
As said on http://wiki.archlinux.org/index.php/Fix … _subsystem I edited grub boot line with 'break=y'
but 'echo /dev/sd* ~hd*' does show nothing. (as a matter of fact it does show the partitions... on arch64 (kernel-2.6.18 ) where I gave a try).
Tried with default kernel-2.6.19 with initrd=kernel26.img as well as kernel26-fallback.img where it simply stops right here :
Please what steps should I go for recovering arch32 in this location ?
Note that I have access to arch32 FS from other distros on the same machine.
# mkinitcpio -M (from arch64, kernel-2.6.18 )
Modules autodetected:
cdrom
ide-cd
ide-core
ide-disk
alim15x3
generic
uli526x
ahci
libata
usblp
usbcore
ehci-hcd
ohci-hcd
usb-storage
ext2
jbd
ext3
jfs
Also I updated the kernel on my laptop (Dell Latitude l400) which has piix and everithing whent fine without editing anything.
Seeded last month: Arch 50 gig, derivatives 1 gig
Desktop @3.3GHz 8 gig RAM, linux-ck
laptop #1 Atom 2 gig RAM, Arch linux stock i686 (6H w/ 6yrs old battery ) #2: ARM Tegra K1, 4 gig RAM, ChrOS
Atom Z520 2 gig RAM, OMV (Debian 7) kernel 3.16 bpo on SDHC | PGP Key: 0xFF0157D9
Offline
If you don't change the mkinitcpio configuration and boot with the normal kernel26.img image, then the device names don't change, everything stays hdXY as it was. Thus you should be able to boot with kernel26.img without changing anything.
The fallback image includes both the libata and the ide modules and seems to load pata first by default. As that fails for you, I guess your pata driver is still experimental and you should stay with ide for now.
Offline
brain0 if you read 1st two lines of my post, you can see I use a Sata HDD, so i do not see how to follow your advice, as IMHO I do not use nor need pata to boot on that drive.
Default archlinux 32 kernel26.img do not boot since upgraded to 2.6.19-ARCH.
Advice more than welcome.
Seeded last month: Arch 50 gig, derivatives 1 gig
Desktop @3.3GHz 8 gig RAM, linux-ck
laptop #1 Atom 2 gig RAM, Arch linux stock i686 (6H w/ 6yrs old battery ) #2: ARM Tegra K1, 4 gig RAM, ChrOS
Atom Z520 2 gig RAM, OMV (Debian 7) kernel 3.16 bpo on SDHC | PGP Key: 0xFF0157D9
Offline
well, as shown in the picture, where it freezes?? ... is where udev takes over (correct em if i'm wrong), it therefore appears to be n issue with the usb modules, might i suggest unplugging any usb devices from the system.
also how does ur rc.conf | modules, and mkinitcpio.cong setup, differ form before the upgrade?
also, as stated by brain0, if didn't modify the mkinitcpio.conf, then the kernel26*img`s r pretty much the same as usual (not using pata), therefore if u go ahead and change the device names in fstab,fi.e then u've got problems.....
The.Revolution.Is.Coming - - To fight, To hunger, To Resist!
Offline
I was referring to the picture: It has pata_ali loaded, but no SATA driver (yet). So it is possible that it fails due to pata_ali. Could you provide a picture from a boot attempt with your default image (which has pata disabled, right?).
Offline
Just some input here from another pata_ali/alim15x3 user (me):
- ide (alim15x3) works fine, no problems
- pata (pata_ali) works alright, but is slower, primary channel (hd) went from UDMA33 to MWDMA2 and secondary (cd) from MWDMA2 to PIO4
1000
Offline
I also have that Asrock board and no problems running the new kernel. Device names didn't change. I also use a sata harddisk to boot.
do have your harddisk connected to sata1/sata2 or to the additional jmicron sata connector?
plase show us your /etc/mkinitcpio.conf.
Offline
Thank you for your help guys . It does helps to see somewhat clearer at least
Hell on me I now know something I did wrong :oops: On arch32, while I stil used kernel-2.6.18 & after I connected HDD to sataII connector, it didn't boot with kernel26.img, but did fine with kernel26-fallback.img. I totally forgot that as I barelly rebooted before updating to kernel-2.6.19
> Could you provide a picture from a boot attempt with your default image (which has pata disabled, right?).
Well I will but is this valuable even with the mistake just mentionned ?
> well, as shown in the picture, where it freezes??
it stops right at the end of the screenshot (waited 5 minutes without seeing anything happends 3 times).
rc.conf | modules, and mkinitcpio.conf were untouched in the upgrade process. I wish I could chroot into arch32 from arch64, but I have this permission/execution error on /bin/bash when I want to chroot (I changed no permission nor /etc/passwd, this error is quite reported in various pages without solution though).
byte > the whole system is on SataII HDD. Should I unplugg (backups) IDE HDD and try to boot again ?
> do have your harddisk connected to sata1/sata2 or to the additional jmicron sata connector?
SataII as mentioned on 1st post, 2nd line
Thank you to report your hardware's workin fine.
AndyRTR > is yours on sataI or SataII connector ? Please could you print your MODULES & HOOKS line in /etc/mkinitcpio.conf ? I'm still with kernel-2.6.18 on arch64 (building custom kernel with morph patchs 2night) ?
Seeded last month: Arch 50 gig, derivatives 1 gig
Desktop @3.3GHz 8 gig RAM, linux-ck
laptop #1 Atom 2 gig RAM, Arch linux stock i686 (6H w/ 6yrs old battery ) #2: ARM Tegra K1, 4 gig RAM, ChrOS
Atom Z520 2 gig RAM, OMV (Debian 7) kernel 3.16 bpo on SDHC | PGP Key: 0xFF0157D9
Offline
2day I plugged back the SataII HDD to one fo the 2 SataI conectors and could arch32 with my custom kernel-beyond. (2.6.17)
As everything went fine, I upgraded the system, edited mkinitcpio.conf with MODULES detected by mkinitcpio -M. Reboot fine.
Then I plugged the HDD back to the SataII connector and booted arch32 w/ kernel-2.6.19, standard .img
System booted, but HDD froze after just a few seconds and gave me the hand back ~2' after. But unusable as it remounted FS ro
Now rebooted in arch64, kernel-2.6.18-ARCH
Post "solved" as I was able to _boot_ Follow-up of freeze prob in this post
Seeded last month: Arch 50 gig, derivatives 1 gig
Desktop @3.3GHz 8 gig RAM, linux-ck
laptop #1 Atom 2 gig RAM, Arch linux stock i686 (6H w/ 6yrs old battery ) #2: ARM Tegra K1, 4 gig RAM, ChrOS
Atom Z520 2 gig RAM, OMV (Debian 7) kernel 3.16 bpo on SDHC | PGP Key: 0xFF0157D9
Offline