0.8 alpha/beta and final Voodoo installation feedback

auditek747 · 2006-12-19 21:39:06

brain0 wrote:

auditek747 wrote:
In order to run "PATA" (which I think is the point of this exercise),
I had to install as follows:
I don't understand. Why didn't you just boot the image without any options? PATA is default then. The ide-legacy option is intended for those who cannot use PATA yet, because of driver bugs or whatever.

It just goes to show you,... I, at first, had a very long post going into all kinds
of detail, but it seemed TOO long so I cut it down.

The default install labels the drives /dev/sdxx , this is fine until time to
install lilo. It fails with the error

Fatal: raid_setup:stat("/dev/hda")

So I needed the ide-legacy for the installer... not to run the machine afterwards.

brain0 · 2006-12-19 21:47:48

auditek747 wrote:

The default install labels the drives /dev/sdxx , this is fine until time to
install lilo. It fails with the error
Fatal: raid_setup:stat("/dev/hda") 
So I needed the ide-legacy for the installer... not to run the machine afterwards.

No, it just seems that the installer doesn't configure lilo properly (I assume it sets the boot= option to hda, but it should be sda). You should use grub instead of lilo anyway.

auditek747 · 2006-12-19 22:04:16

brain0 wrote:

auditek747 wrote:
The default install labels the drives /dev/sdxx , this is fine until time to
install lilo. It fails with the error
Fatal: raid_setup:stat("/dev/hda") 
So I needed the ide-legacy for the installer... not to run the machine afterwards.
No, it just seems that the installer doesn't configure lilo properly (I assume it sets the boot= option to hda, but it should be sda). You should use grub instead of lilo anyway.

Sorry, I was just about to edit my previous post and had to go offline for a
minute.
The installer prompts you to check/edit the lilo.conf before installing.
I tried it both ways doing two different installs, and succeeded on the third
install with the method I described earlier, and you should use lilo instead
of grub anyway , I shouldn't use a crusty old Gateway laptop!

scottro · 2006-12-19 22:41:52

It didn't recognize my CDROM drives. (They're about 5 years old, as I said.)
So, I chose ide-legacy and everything was fine.

Had I done a simple upgrade, I doubt I would have even noticed that it's a new release version.

This is an older machine. However, it had no problem redoing the IDE hard drives as sdxx.

I did try playing with /etc/fstab and menu.lst as per auditek747's advice, but it wouldn't boot, giving me a panic. I'm not sure what I did wrong but I won't have time to play with it until the weekend.

auditek747 · 2006-12-19 23:40:35

scottro wrote:

It didn't recognize my CDROM drives. (They're about 5 years old, as I said.)
So, I chose ide-legacy and everything was fine.
Had I done a simple upgrade, I doubt I would have even noticed that it's a new release version.
This is an older machine. However, it had no problem redoing the IDE hard drives as sdxx.
I did try playing with /etc/fstab and menu.lst as per auditek747's advice, but it wouldn't boot, giving me a panic. I'm not sure what I did wrong but I won't have time to play with it until the weekend.

I'm not sure if I should respond here, as I made a mistake during my install.
brain0 was right, and I can boot the default install, and the only problem is
that the auto generated lilo.conf has an incorrect "boot=" description.
I should have listened

I think, if you really have to use ide-legacy, you need to keep the
/dev/hdxx references, and the reason for the kernel panic lies elsewhere.

scottro · 2006-12-20 00:14:05

Ahh--ok, that makes a difference, I think, and makes much more sense.

Thank you.

brain0 · 2006-12-20 00:35:53

Why are you all so confused? The point of the installer is to make things work without manipulating all that stuff manually. I will take care of lilo before 0.8.

scottro · 2006-12-20 01:05:22

My confusion was simply in perhaps misreading auditek747's post.

In my case, the aging hardware doesn't work properly with the default boot, so I would have (had I not seen any of this, and simply downloaded and booted the CD) would have, after I saw that it found no CD drive, have rebooted with ide-legacy. The default grub created works with that, and everything is fine.

So yes, the installer, and the messages it gives after the first hit of enter, should do the job. Sorry if I've made it sound more complex than it was. As always, the developers have done an excellent job.

A newcomer, would probably do this--they might do the default boot. They might (again, if they had hardware like mine) see that it wasn't working--there were a few error messages during boot that were repeated, but seemed to sort themselves out--however, even if they decided to be brave and continue they would see that it couldn't find the CDROM.

Then, as they had seen the message after hitting enter for the first time, they would realize, hopefully, that they should try again with ide-legacy. At that point, everything would work quite well for them. (As it did for me.)

So, yes, you're doing a great job with the installer and it is working as it should. (If that sounds sarcastic, it isn't, as I said at the beginning of this overly long post, I simply misread auditek747's original post. He saw this and corrected my misunderstanding.

byte · 2006-12-20 01:13:30

brain0 wrote:

No, it just seems that the installer doesn't configure lilo properly (I assume it sets the boot= option to hda, but it should be sda). You should use grub instead of lilo anyway.

Aaargh, I've checked everything else, but that little innocent "boot=/dev/hde" up there in lilo.conf escaped me.
You win.

judfilm · 2006-12-20 01:57:05

Hi, could someone elaborate on this change:

"Changelog to older isos:
20061217
- fixed ext3 creation defaults"

Thanks

brain0 · 2006-12-20 10:30:23

It seems mirror syncing is going faster now. At least our main ftp mirror has synced and you can get the alpha isos here: ftp://ftp.archlinux.org/other/0.8/

soloport · 2006-12-20 15:54:43

Apparently IDE vs PATA does matter.

Was having trouble with new installation. Started with old ISO, but did FTP installation, so ended up with "Arch Linux 0.8 (Voodoo)".

First attempt to fix kernel panic was to switch HDD partitions from /dev/hdaN to /dev/sdaN in fstab and in grub. When that didn't resolve the problem, then tried lots of combinations at grub prompt.

M/B doesn't have Intel chipset (so legacy piix didn't apply). Tried rootfstype=ext3 because, just before kernel panic, was complaining about file type. The thing that made everything work was to remove the CD-ROM and also use /kernel26-fallback.img doing just one or the other didn't work -- so, you can imagine it took many hours to figure this out.

Afterward, noted the difference between regular and fallback and reverted back to /kernel26.img by changing /etc/mkinitcpio.conf from default:
- HOOKS="base udev autodetect ide scsi sata filesystems"
To:
- HOOKS="base udev autodetect pata filesystems"
(Don't need a CD-ROM attached)

HTH

BTW, Voodoo boots quite a bit faster than Gimmick (using subjective metrics, of course). Nice job!

aRcHaTe · 2006-12-20 16:32:39

everything is working JUST fine...im on nirvana

brain0 · 2006-12-20 16:54:37

soloport: the topic of this thread is discussion of the new alpha isos, not everything else. If you can't use the new iso, then would you please tell us why and leave the rest into another thread. The new iso tries to autoconfigure mkinitcpio.conf so that you never have to touch it again, the old one doesn't.

soloport · 2006-12-20 17:34:58

brain0 wrote:

soloport: the topic of this thread is discussion of the new alpha isos, not everything else.

Yes. (My bad. Thought because ended up with "Voodoo" it might be applicable.) Will install both ISOs (i686 i86_64), tonight. Thanks.

mandos · 2006-12-20 18:49:32

I don't know if this should be discussed to another thread:

beyond kernel is panicking (default kernel is still ok)
I tried to add earlymodules=piix, it didnt work!

everything else is just fine, I'm trying to convince my brother to give Arch a try (and stop speaking about bsd )
if I manage it I'll give report for a laptop with sata (though I believe everything will work!)

brain0 · 2006-12-20 22:44:53

mandos wrote:

beyond kernel is panicking (default kernel is still ok)
I tried to add earlymodules=piix, it didnt work!

That workaround is no longer needed/working for 0.8 systems, the installer makes sure that the correct modules are always loaded. It was only intended as a workaround for older systems, as the update to 2.6.19 unevitably switched from piix to ata_piix for those with Intel chipsets.
I think we need to make sure that people doing a 0.8 install don't get that message any more, somehow.

Can you provide more details about the beyond issue? Is it a 2.6.19 version?

desertViking · 2006-12-21 04:26:22

I've had great results so far, and I've bent it pretty far out of shape. It looks good. I used the "current" ISO, 686.

byte · 2006-12-21 04:31:07

One thing I noticed that's different with -beyond is that libata is builtin, as opposed to being a module in -ARCH and -ck.

Moo-Crumpus · 2006-12-21 10:43:25

It boots until

booting Arch Linux Install ...
..
/initrd /boot/initrd.img
[Linux-initrd .... bytes]

and freezes then.

I run sata and scsi devices (aic7xxx, sata_sil, sata_promise).

Neither noapic, nore acpi=off, pci=routing or nosmp helps me.

solstice · 2006-12-21 17:29:43

hi.
i tested base-0.8-20061218-i686.iso.
all went fine.

i just booted into that new arch and login as root. just to check all was fine that's all.

during the configure phase
when you got help screen for /etc/mkinitcpio.conf

i read

if you do not have US keyboard use keymap HOOK

is that a typo ? and US should not be instead USB ???

i really don't understand what the fact to have a non US keyboard has on the choice of HOOK

hightower · 2006-12-21 19:05:25

@ solstice

In the early stages of booting, your system supports only the US keyboard layout. If something goes wrong, people with other keyboard layouts have a problem because they don't know which key to press. Another point is that specific letters aren't available so it isn't possible to enter the password for a encrypted partition properly for example.

With the HOOK keymap you assure that your keyboard layout is properly supported in early userapace.

hightower

amdviaman · 2006-12-21 19:47:32

Just installed it on my notebook (HP Pavilion DV5215us) and everything is running very nicely, however there seems to be a problem with ndiswrapper and the 2.6.19 kernel. WiFi works fine for extended peroids of time as long as I don't use any of KDE's network monitoring/manipulation tools (kwifimanager and knemo). When I do use them,
after about a minute the whole system locks (no entering VT's or breaking out of X) the mouse even stops moving and the machine needs to be manually restarted. I cannot even get dmesg output because when it locks I cannot even ssh into it, total kernel lock. This was also an issue in 0.7.2 when I upgraded to 2.6.19 (from 2.6.18.1). At one point after trying to trigger the crash at runlevel 3 as root, when I closed X and re-entered runlevel 5 the kernel dumped a bunch of output. Though it seemed to have crashed, the terminal was still usable via the mouse with gpm by pasting in characters on the screen and forming them into commands, but would take no input from the keyboard whatsoever.
Another time when rebooting after the crash I was presented with the same kernel dump at bootup but I could not record it as it didn't seem to get logged. Though the keyboard was still usable, the system would not contiinue to boot. Referenced source file related that crash was arch/i386/himem.c on line 42.

The crash continues no matter what i enable/disable (fglrx, hal, dbus, acpid, etc) all yeild an eventual lockup when using knemo or kwifimanager.

More info about this hardware:

00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 01)
00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:05.0 PCI bridge: ATI Technologies Inc Unknown device 5a37
00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller
00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 11)
00:14.1 IDE interface: ATI Technologies Inc Standard Dual Channel PCI IDE Controller ATI
00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge
00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge
00:14.5 Multimedia audio controller: ATI Technologies Inc IXP SB400 AC'97 Audio Controller (rev 02)
00:14.6 Modem: ATI Technologies Inc ATI SB400 - AC'97 Modem Controller (rev 02)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:05.0 VGA compatible controller: ATI Technologies Inc ATI Radeon XPRESS 200M 5955 (PCIE)
06:02.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
06:04.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
06:04.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller
06:04.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller
06:04.4 Generic system peripheral [0805]: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller
06:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

Graphics adapter is an ATI Xpress 200M.
Other then that nice job on Voodoo, everything else seems to work very well and the installer additions and module pre-configuration are a welcome change.

fk · 2006-12-21 21:41:57

The FTP-ISO works without any problem on an Thinkpad X60s with external USB DVD-ROM

Mr.Elendig · 2006-12-21 23:34:51

FTP install on a 939Dual-SATA2 with an amd X2 (ULi M1695 chipset)

Nothing special to report, exept that the new pata driver gave me a kernel panic at boot from the install cd. Legacy driver worked ok. Booted just fine after install tho. (using hwdetect to set up mkinitcpio and rc.conf)

Arch Linux

#26 2006-12-19 21:39:06

Re: 0.8 alpha/beta and final Voodoo installation feedback

#27 2006-12-19 21:47:48

Re: 0.8 alpha/beta and final Voodoo installation feedback

#28 2006-12-19 22:04:16

Re: 0.8 alpha/beta and final Voodoo installation feedback

#29 2006-12-19 22:41:52

Re: 0.8 alpha/beta and final Voodoo installation feedback

#30 2006-12-19 23:40:35

Re: 0.8 alpha/beta and final Voodoo installation feedback

#31 2006-12-20 00:14:05

Re: 0.8 alpha/beta and final Voodoo installation feedback

#32 2006-12-20 00:35:53

Re: 0.8 alpha/beta and final Voodoo installation feedback

#33 2006-12-20 01:05:22

Re: 0.8 alpha/beta and final Voodoo installation feedback

#34 2006-12-20 01:13:30

Re: 0.8 alpha/beta and final Voodoo installation feedback

#35 2006-12-20 01:57:05

Re: 0.8 alpha/beta and final Voodoo installation feedback

#36 2006-12-20 10:30:23

Re: 0.8 alpha/beta and final Voodoo installation feedback

#37 2006-12-20 15:54:43

Re: 0.8 alpha/beta and final Voodoo installation feedback

#38 2006-12-20 16:32:39

Re: 0.8 alpha/beta and final Voodoo installation feedback

#39 2006-12-20 16:54:37

Re: 0.8 alpha/beta and final Voodoo installation feedback

#40 2006-12-20 17:34:58

Re: 0.8 alpha/beta and final Voodoo installation feedback

#41 2006-12-20 18:49:32

Re: 0.8 alpha/beta and final Voodoo installation feedback

#42 2006-12-20 22:44:53

Re: 0.8 alpha/beta and final Voodoo installation feedback

#43 2006-12-21 04:26:22

Re: 0.8 alpha/beta and final Voodoo installation feedback

#44 2006-12-21 04:31:07

Re: 0.8 alpha/beta and final Voodoo installation feedback

#45 2006-12-21 10:43:25

Re: 0.8 alpha/beta and final Voodoo installation feedback

#46 2006-12-21 17:29:43

Re: 0.8 alpha/beta and final Voodoo installation feedback

#47 2006-12-21 19:05:25

Re: 0.8 alpha/beta and final Voodoo installation feedback

#48 2006-12-21 19:47:32

Re: 0.8 alpha/beta and final Voodoo installation feedback

#49 2006-12-21 21:41:57

Re: 0.8 alpha/beta and final Voodoo installation feedback

#50 2006-12-21 23:34:51

Re: 0.8 alpha/beta and final Voodoo installation feedback

Board footer