You are not logged in.
This seems completely unrelated to the install ISO - start a new topic and ask for help there.
Offline
My bad... ahem... I figured out what was the cause, Gnome is missing gnome-terminal mayhap this can be passed on to the Gnome package maintainer. As for the RC iso, toofishes was correct, the installer worked like a charm for me although I would like to point out that excluding km is not a good idea.
Anyway ignore me (except for the gnome-terminal missing as a part of the gnome package)
Sorry
EmyrB
Proud Arch Linux User
Offline
I used the FTP Install iso image to install Arch on my Macbook this weekend. No problems at all...
Zeq
"Till shade is gone, till water is gone, into the Shadow with teeth bared, screaming defiance with the last breath, to spit in Sightblinder's eye on the Last Day"
Offline
This is no KISS philosophy.
This is an unfortunate first step towards complete ubuntization of Arch.
+1 flamebait
Part of KISS, is knowing what exactly happens on your system.
With UUIDs you do not know what happens.
An extravagant, useless, additional - and complex, not KISS - layer of information, gets between you and your system.
You do not know anymore how kernel truly enumerates disk controllers and their channels.
Sure I do. It enumerates your partitions in /dev/disks/by-uuid EVERY time. Also, I'd appreciate a more coherent suggestion of what to do instead. I mean, if solving this problem by using UUIDs is such a crime, clearly you must have a better solution in mind, right? Wouldn't want to commit a greater crime by being an ass about something you know nothing about...
Shame on whoever is behind this.
Oh I feel teh shame.
The suggestion box only accepts patches.
Offline
Let's be civil now. This is about the installer and ISO, not about decisions we have made. If you have an alternative to using UUIDs (i.e. using udev's persistent disk rules), please start a new thread or a bug report. It has nothing to do with this thread
Offline
I've tried the core- and ftp iso-images and they work fine. The .img's for bootable USB-sticks have a flaw though. I have two systems that won't boot off USB with this release. The problem is that my harddisk is being detected as sda, and then my usbstick as sdb, and fstab from the USB-stick tries to mount sda. Just as the installer now defaults to using UUID's in fstab and grub, it should also be used on the usbstick images. I had my own usb-stick Arch installation and used UUID's there. It works fine. I also like to see a grub option to add "rootdelay=8" to the kernel paramenters, it is required for some systems which detect usb-devices too slow.
Offline
The .img's for bootable USB-sticks have a flaw though. I have two systems that won't boot off USB with this release. The problem is that my harddisk is being detected as sda, and then my usbstick as sdb, and fstab from the USB-stick tries to mount sda. Just as the installer now defaults to using UUID's in fstab and grub, it should also be used on the usbstick images. I had my own usb-stick Arch installation and used UUID's there. It works fine.
I need more details on this, can you post any relevant output leading up to it being unable to mount?
I also like to see a grub option to add "rootdelay=8" to the kernel paramenters, it is required for some systems which detect usb-devices too slow.
That sounds like a good idea, added it to a todo list.
The suggestion box only accepts patches.
Offline
jealma wrote:The .img's for bootable USB-sticks have a flaw though. I have two systems that won't boot off USB with this release. The problem is that my harddisk is being detected as sda, and then my usbstick as sdb, and fstab from the USB-stick tries to mount sda. Just as the installer now defaults to using UUID's in fstab and grub, it should also be used on the usbstick images. I had my own usb-stick Arch installation and used UUID's there. It works fine.
I need more details on this, can you post any relevant output leading up to it being unable to mount?
jealma wrote:I also like to see a grub option to add "rootdelay=8" to the kernel paramenters, it is required for some systems which detect usb-devices too slow.
That sounds like a good idea, added it to a todo list.
Yes, output is as follows:
USB Mass Storage support registered.
scsi 6:0:0:0: Direct-Access BUFFALO USB Flash Disk 4000 PQ: 0 ANSI: 0 CSS
sd 6:0:0:0: [sdb] 8093696 512-byte hardware sectors (4144 MB)
sd 6:0:0:0: [sdb] Write Protect is off
sd 6:0:0:0: [sdb] Assuming Drive cache: write through
sd 6:0:0:0: [sdb] 8093696 512-byte hardware sectors (4144 MB)
sd 6:0:0:0: [sdb] Write Protect is off
sd 6:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 6:0:0:0: [sdb] Attached SCSI removable disk
:: Scanning for boot usb device...
EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as ext2
EXT2-fs warning (device sda2): ext2_fill_super: mounting ext3 filesystem as ext2
failed to mount /dev/sda3
Attempt to access beyond end of device
sda4: rw=0, want=4, limit=2
EXT2-fs: unable to read superblock
failed to mount /dev/sda4
failed to mount /dev/sda5
failed to mount /dev/sda6
failed to mount /dev/sda7
failed to mount /dev/sda8
ERROR: cannot find booted usb device, cannot continue...
Kernel panic - not syncing: Attempted to kill init!
This is everything I can read on my display when it stops. All the stuff about failing to mount /dev/sda4 and others has to do with my first harddrive, which on boot is recognised as /dev/sda, and contains eight partitions (sda1, sda2, sda3, sda5, sda6, sda7 and sda8; sda4 is extended). The problem is that the GRUB-entry and the FSTAB-entry's on the bootable Arch USB-image use /dev/sda as root device, while they should be using UUID's. Using UUID's, the order of detecting harddrives does not matter anymore, because a partition will always have the same UUID. Of course LABELS are also an option.
If you need more information, please ask.
Edit: Sometimes the system seems to boot, even if my USB-stick is detected as /dev/sdb, very weird. And when booting, it throws open my cdrom tray (NEC 7173S SATA dvd-writer on motherboard with AMD 770 chipset and AMD SB600 southbridge).
Last edited by jealma (2008-04-22 20:51:03)
Offline
i get the same cdrom eject behavior on my laptop using the i686 usb img. otherwise everything works as i would expect. if necessary, i will post hw information on my cd drive once i can get my hands on my laptop this evening.
Last edited by rson451 (2008-04-22 22:06:39)
archlinux - please read this and this — twice — then ask questions.
--
http://rsontech.net | http://github.com/rson
Offline
Simo, what do you think of providing an option to create /disk-by-label during the install?
....or if you think it is more KISS, I could modify the Beginner's Guide to provide an alternative method of adding partition labels from vc2 on the live cd, for those who have an aversion to uuid.
Offline
We're organising a Linux install party in my school tomorrow. I'm going there with a few ISOs and two USB drives (one with x86_64 and one with i686), that will give me an occasion to test.
And yes, the Don't Panic ISO is fallback, just in case
Offline
@catwell: where are the ubuntu 8.04 cd's?
Last edited by Eliteforce (2008-04-26 09:16:39)
Offline
We're organising a Linux install party in my school tomorrow. I'm going there with a few ISOs and two USB drives (one with x86_64 and one with i686), that will give me an occasion to test.
And yes, the Don't Panic ISO is fallback, just in case
Good luck! Even if people don't find Arch to be there thing right off the bat, it's still great you're getting the name out there!
Props to you my friend!!!
Offline
News from the install party: it was a failure for Arch I guess. Everybody wanted the new Ubuntu 8.04, and nobody wanted to install Arch, which they'd newer heard about. I still reinstalled one of my own laptops (i686) with the new ISO and it worked just fine.
Oh, I still think it made a few people learn about Arch, maybe they'll come to it when they'll be fed up with Ubuntu. After all Arch isn't really suited for people who come to this kind of events (linux beginners). All those I've converted before (makes it 4 people I think) were already regular Linux (Gentoo or Debian) users. We used the flash drives and ISOs a lot though, not to install but to fix problems on other PCs such as partitioning (with cfdisk) and reinstalling Grub on a Mac. And, of course, to play space invaders too
Offline
I downloaded the usb image for a normal core installation last night. As of now, however, I cannot get Arch to install properly because each time I went to try to install it I was met with circular dependency issues. The errors basically said installing gcc+ would be installing files older than what is already in place?! It was late so I may not have the error 100% correct. I made sure the md5sums were correct and that the .img files were written to the usb stick without error.
If theres anything I can do to help debug this I'll be happy to supply whatever else I can because I really want to use the usb images from now on instead of bothering with cd's.
MS
Offline
How do I put the image on a USB stick in Windows?
Offline
You can try dd for Windows but I'd go for a Linux Live-CD.
Offline
@catwell: I have an archlinux install, was just wondering if it's possible on windows. dd for windows seems promising.
Okay, got it on my usb stick. Checked the md5 hash of the image before I put it on the stick.
Did: dd if=arch-core-install-2008.04-rc-i686.img of=/dev/sdc
Rebooted, and entered Bios and set first boot device to USB-FDD. It doesn't boot, it just loads grub from my HDD. Any ideas?
Offline
Did: dd if=arch-core-install-2008.04-rc-i686.img of=/dev/sdc
Rebooted, and entered Bios and set first boot device to USB-FDD. It doesn't boot, it just loads grub from my HDD. Any ideas?
Found this in the wiki:
"Some BIOS are not smart enough (like mine) to detect that a USB device was connected. If this is your case, just use "Pause Break" to connect you pen drive in a very early boot stage. Also, if available on your BIOS, prefer using F12 boot menu. "
Zl.
Offline
Large USB sticks are recognised as removable hard-drives, so sometimes it will need to be booted as USB-HDD. You should try checking the hard drives boot order in your BIOS - sometimes you can see the stick there - just select it as a first drive. You should also check if you have "Enable legacy USB drives" option enabled in BIOS (may be called a little different depending on the BIOS manufacturer).
P.S. I had no luck booting from USB either - I tried uploading the arch-ftp-install-2008.04-rc-i686.img file on Windows and on Linux, but after the uploading my stick was unaccessible (no file system present) and computer hanged during boot when discovering stick. And the stick is 100% fine - every other bootable distro went on it without any problems.
Last edited by Corey (2008-04-28 19:08:57)
Offline
Any estimated time frame for the "final" release of 2008.04/05?
Offline
As of now, however, I cannot get Arch to install properly because each time I went to try to install it I was met with circular dependency issues. The errors basically said installing gcc+ would be installing files older than what is already in place?! It was late so I may not have the error 100% correct.
MS
I'm having the same problem.
Offline
MoonSwan wrote:As of now, however, I cannot get Arch to install properly because each time I went to try to install it I was met with circular dependency issues. The errors basically said installing gcc+ would be installing files older than what is already in place?! It was late so I may not have the error 100% correct.
MS
I'm having the same problem.
Could you please report the *exact* error? "Something like an error with a thing and some stuff" is far from helpful.
Offline
Could you please report the *exact* error? "Something like an error with a thing and some stuff" is far from helpful.
My apologies Phrakture, at the time I posted this I was rather spaced out on my pain meds. I will try again to install from the usb image file. [deleted content, this was user error & QtParted bugs which is irrelevant to this thread].
Last edited by MoonSwan (2008-05-03 22:07:38)
Offline
installed from the x86_64 ftp iso worked almost perfect. only annoyance is the time issue for which there is already a bug about. neotuli's way of solving this (adding clock=UTC timezone=foo/foo2 to grub line) didnt seem to work
There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums. That is why we avoid it. -- ewaller (arch linux forum moderator)
Offline