Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#33803 - Cannot Get Working Install from February 2013 dual iso image
Attached to Project:
Arch Linux
Opened by Oliver H. Bailey (oliverhbailey) - Sunday, 10 February 2013, 18:53 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Monday, 11 February 2013, 02:44 GMT
Opened by Oliver H. Bailey (oliverhbailey) - Sunday, 10 February 2013, 18:53 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Monday, 11 February 2013, 02:44 GMT
|
DetailsDescription: The February 2013 dual iso - does not install a working system an ASUS M5A78L-M LX Plus series motherboard. I just replaced an older Intel pentium running the current Arch Linux updated with PACMAN monthly since July 2012, using Syslinux and the new installation boots missing /sbin/init. When I use the append command to set the partition for root=/sda1 and boot=/dev/sda2 the sysme boots but no ethernet drivers, utilities, or network drivers and utilities are found. I use the Installation wiki instructions and installed the base and base-devel using pacstrap and syslinux after arch-chroot, using pacman.
I install and modify Arch kernels and write device drivers on a regular basis for real-time applications and gaming without issue. I went on to install Mint 14, x64 without incident and without any hardware issues at all. This machine has 8 GB of RAM, three hard drives (500 MB, and 2 - 1.5TB drives). I did notice during installation that a little extra effort was need to get DHCPCD working with the link. I had to bring down the link, issue a DHCPCD command and then bring the link back up when I can usually bring the link down and let DHCPCD start the link and obtain an IP address. There is a mention of this problem on the wiki from 2/8/2013 under a different thread comparing Syslinux to Grub. I install several Arch systems a month and this is the first time a BIOS based MBR system has had problems booting with Arch and Syslinux. Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: |
This task depends upon
Closed by Gerardo Exequiel Pozzi (djgera)
Monday, 11 February 2013, 02:44 GMT
Reason for closing: Not a bug
Additional comments about closing: Please use forums to get a better support. This place is only for reporting bugs. Thanks
Monday, 11 February 2013, 02:44 GMT
Reason for closing: Not a bug
Additional comments about closing: Please use forums to get a better support. This place is only for reporting bugs. Thanks
Comment by Dave Reisner (falconindy) -
Monday, 11 February 2013, 00:14 GMT
/sbin/init is a symlink provided by systemd-sysvcompat, which is in base. If you don't have this symlink in a new install, you've done something extremely wrong. This is nothing new. It's been the default for the past several ISOs.