[Solved] Installing arch on a notebook /w a 2.6.33+ chipset

Hi,
quick question:
I'd like to install arch on a notebook with a chipset that is not supported until 2.6.33.
The installation images however look rather old, so I'm afraid i won't even get to the installation step where I can chose which kernel to install.
What's the best way to do this?
*fixed typo
Last edited by Zoranthus (2010-04-22 13:41:01)

If you're referring to the Arrandale Chipset then you probably won't have any trouble with the official installation image. I used it to install a Clarkdale system without any trouble at all. The system even ran fine with 2.6.32 kernel.
You should use ethernet to connect to the internet during the installation though since your laptop probably has a very new wifi card too. If you choose netinstall you'll get 2.6.33.2-1 or later and you'll be good to go.
Regards,
demian
Last edited by demian (2010-04-20 13:27:23)

Similar Messages

[Solved] Install Arch 64 on new hardware (Intel I7-860, P55, Nvidia 46

Hi,
I just installed new hardware in my computer and wanted to install Arch Linux 64Bit on it. I got through the installation as usual, no special configuration done here. Then I tryed to boot my computer into ArchLinux which fails as after GRUB I only see a black screen.
I tried many different screen resolutions so that's not the problem. I waited for at least 5min but the screen stays black.
This is my hardware setup:
- Asus P7P55D Pro (Intel P55 Extreme Chipset)
- Intel i7-860
- MSI N460 GTX Hawk
- 8GB DDR3 Ram
I honestly have no idea what could cause the problem. Something special regarding kernel version, os configuration that i missed? I appreciate your help.
Thanks,
aXyde
Last edited by aXyde (2011-01-17 12:31:31)

After I saw this thread https://bbs.archlinux.org/viewtopic.php?id=111805 which described a similiar problem to mine I added "nomodeset" to the kernel command line and all is working fine.

[SOLVED] Install Arch Linux on USB Stick!

So, here is the deal. I want to install Arch Linux on a USB Stick so I can plug it at any computer and have my system... with me
I've had a little bit experience with Arch so I know a few things about it... used it for a few months before on a real system.
My USB stick is a HighSpeed 17-20 MBPS and it's 16 GB capacity.
So how do I do it?
Last edited by 1lj4z1 (2012-04-05 07:25:53)

I'm using occasionally Arch installed on HDD-USB, I've just added usb hook to mkinitcpio.conf and removed autodetect (more modules=more hardware supported). So far it worked on 3 different computers (all of them have one main HDD so no grub issues, but it's no biggie if it doesn't boot right away, you can always edit grub on-the-fly by pressing "e")
About USB stick: installing on USB stick is not the same as running it in LIVE mode! Consider yourself warned.
If you just install it you really should read about SSD optimizations because USB flash cells also have limited read/write cycles (actually is less robust and sophisticated than SSD). Something to look at: noatime mount option, disable swap if not necessary, profile-sync-daemon and so on...
1lj4z1 wrote:Well I don't need to chroot, i am running it live. I'll see about mkinitcpio.conf but I can't understand what you mean rebuilding initramfs? What is that exactcly?
It means if you fiddle with mkinitcpio you should run:
# mkinitcpio -p linux
afterwards or bad things will happen
Last edited by masteryod (2012-03-27 15:37:13)

[SOLVED] Installed Arch on IBM A22m laptop, startx fails

I installed arch on this old laptop IBM A22m and I am trying to get XFCE4 or LXDE working on it.
When i start xfce4 i get "server terminated with error(1)" and same thing with lxde but this time i get to see panel and wallpaper for 2 seconds before it crashes.
I tried exec openbox-session and it wont crash until I open browser from terminal.
Here is xorg.0.log i get from crashed openbox-session: http://pastebin.com/SK9Vvunp
00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
00:02.0 CardBus bridge: Texas Instruments PCI1450 (rev 03)
00:02.1 CardBus bridge: Texas Instruments PCI1450 (rev 03)
00:03.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 0c)
00:03.1 Serial controller: LSI Corporation LT WinModem (rev 01)
00:05.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24/30 [CrystalClear SoundFusion Audio Accelerator] (rev 01)
00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rage Mobility AGP 2x Series (rev 64)
Here is hwinfo: http://pastebin.com/wWePzduM
uname -r 3.16.4-1
I am using xf86-video-mach64 driver.
Help needed =P
Last edited by sahtimonni (2014-10-13 15:16:02)

This is a bit outside my experience - but did you follow the advice and cautions in the wiki for that driver:
https://wiki.archlinux.org/index.php/Mach64

[SOLVED] install arch VM with pacstrap

Dear all,
I am installing a Arch VM on my Arch host. The host is up-to-date, well configured (at least I think) in a vanilla manner (no suspicious hacks).
# pacstrap -i -c -d /dahlia base base-devel
is installing all packages but gives me this error many times:
/usr/bin/bash: error while loading shared libraries: libreadline.so.6: cannot open shared object file: No such file or directory
error: command failed to execute correctly
Googling this error returns lot of topics but I couldn't find a clear answer. I do not want to start with a semi-broken arch VM, so I want to solve this issue before going further.
Thank you
Last edited by gabx (2014-02-10 13:22:42)

# pacstrap -i -c -d /dahlia base base-devel readline lib32-ncurses ncurses acl attr gettext
did the trick

[Solved] Installed Arch, I have a kernel problem.

Hi guys, I'm new here, but I use only linux since 2003. I have a problem at boot... When I choose arch from the bootloader I get this:
ERROR: Failed to parse block device name for '/dev/sda6'
ERROR: root fs cannot be detected. Try using the rootfstype= kernel parameter
Or something very very similar. I see that I'm not the only one experiencing this problem so I try solving by myself following hints I've found on this forum... but nothing changed.
I need help
This is what you have to know:
/etc/mkinitcpio.conf:
MODULES=""
HOOKS="base udev autodetect pata keymap filesystems"
I also tried with ide...
fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/cdrom /mnt/cdrom iso9660 ro,user,noauto,unhide 0 0
/dev/cdrom1 /mnt/cdrom1 iso9660 ro,user,noauto,unhide 0 0
/dev/dvd /mnt/dvd udf ro,user,noauto,unhide 0 0
/dev/fd0 /mnt/fd0 vfat user,noauto 0 0
/dev/sda2 swap swap defaults 0 0
/dev/sda6 / ext3 defaults 0 1
grub entry:
#Archlinux
title ArchLinux (on /dev/sda6)
root (hd0,5)
kernel /boot/vmlinuz26 root=/dev/sda6
initrd /boot/kernel26.img
savedefault
boot
Last edited by Raffo (2007-07-14 16:34:42)

That's very curious. I'm just having this problem after installing the lowlatency kernel from this repo:
Server = http://arch.madfire.net/proaudio/i686
So I've just changed the initrd /boot/kernel26.img to /boot/kernel26rt.img and I'm getting exactly the same error. I've also tried changing sda with hda in the grub's menu.lst but nothing changed...

[SOLVED] Installing Arch x86_64 to HP Chromebook 14 Model 14-q013 4GB

Hello All,
I've had success installing a basic Arch system to my HP Chromebook 14 Model 14-q013sa 4GB, but only if selecting x686 instead of x86_64
The result is, (it's very early days, so please excuse any mistakes) Gnome reporting only 2GB RAM
free -m lists 2010 Total also.
I have tried pressing TAB on the x86_64 install and adding mem=4G or mem=4GB but it simply re-boots.
Any ideas at all for installing the 64bit version of Arch please?
Many thanks everyone.
Last edited by frazer (2014-05-13 13:48:18)

It seems that chromebook has an Intel® Celeron® 2955U processor (http://store.hp.com/UKStore/Merch/Produ … U&sel=PCNB)
https://en.wikipedia.org/wiki/Celeron_2 … C_22_nm.29
Looks like it should be a 64-bit processor.

[SOLVED] Installing arch linux using dd from anrdoid phone's sd card

Hello everybody, I'm totally new and totally excited about arch linux.
I'm trying to create a bootable android phone for some hours now with no success.
The reason I'm trying to do that, is because all my usb sticks are all over the place at friends houses.
Since I'm not the patient type, I decided to do it with my Android Phone's SD card cause I noticed that I have the option to boot from it during startup.
Now, what seems to be the problem is this:
I did "dd bs=4M if=/path/to/archlinux.iso of=/dev/sdc" which seemed to do the job. When I rebooted tho, I didn't see my phone as a booting option.
That was obviously due to unrecognized file system format. How can I dd and keep the filesystem type? I believe that it's ntfs or FAT.
I also tried to install without overwriting the stick, which was a failure, it said it wouldn't find the .cfg files when i ran the commands in the wiki.
Can somebody help me with this?
Thanks in advance
Last edited by deus_deceit (2013-02-10 02:13:12)

Yes, my phone's card works without adding software as soon as I plug it in, the problem appears to be this: when i do "dd" on the SD card the filesystem type changes which causes my phone thinking that the SD card is empty since it doesn't recognize that format and not showing as a bootable device. As soon as I format it with my phone and reboot, it's there. So what I want to do is, create a bootable SD card that keeps the filesystem format that my phone recognizes. Is that possible?
Last edited by deus_deceit (2013-02-10 00:58:54)

[SOLVED] Installing Arch on usb stick - login to emergency mode only

I have checked fstbe which is correct
block is in HOOKS line. Also added ext4 to MODULES
not but not least, i have used that usb for live distros and full installs. also portioned with gparted
most attractive errors in log are
kvm disabled in bios (i am installing only 32 bit version, booted to 32bit)
can not execute plymouth
any ideas
thanks in advance
Last edited by Archhotep (2013-03-25 13:19:28)

WonderWoofy wrote:
Archhotep wrote:
Trilby wrote:It will continue working until you change what usb's are plugged in again. If you want a real solution use UUID in fstab.
I understand that. but both UUIDs and devices (/dev/sdX) are there in fstab if I am correct. I will check that in evening. if so did i make a mistake in generating fstab.
I have generated fstab with
genfstab -p /mnt >> /mnt/etc/fstab (does this happens if i forget -p).
as I have done this multiple times, I might have done some thing wrong. I will edit that file manually and removed /dev/sdx entries from that
Honestly, you are not very good at sharing what is actually in your configs. So as Trilby said above, no one really knows what is in your fstab, since you have not actually shared that with this thread.
As far as I can tell, when I run "genfstab -p /" on my running machine, letting the output just be dumped to stdout, it doesn't give me UUIDs anywhere. And from your statement it seems you haven't even actually checked.
What I have done in the past is used labels. For example if you are using ext2, ext3, or ext4, you could assign a label using "e2label". So lets say you label your rootfs (/) "usb_root". Now instead of using the unreliable /dev/sdXY format, you can use LABEL=usb_root in your fstab, and in the bootloader you can use root=LABEL=usb_root (or root=/dev/disk/by-label/usb_root).
I would also like to mention that this quote sucks:
Archhotep wrote:No. UUIDs are there in the boot loader (I think) and grub was working fine and why the system is trying to boot at first place.
There are a number of people who are patiently trying to walk you through this issue (with quite a bit more hand holding that usually takes place around here), and you don't have the decency/appreciation to even take the time to confirm what you are actually using in the configs that everyone is telling you to check and/or change.
Sir,
I was a standard linux (i mean ubuntu etc) user until sometime back. I don't know exactly what should be there in /etc/fstab. I also do not know what information you might need to help me. If any one asked me the details about /etc/fstab etc might have provided. I have given what info what I felt was appropriate and enough. I do not have that machine with me when I was posting lat post, otherwise I might have posted. that laptop is at home. I already said thanks in my third post immediately after I solve the problem.
Sorry if I am wrong, and thatnk you once again for letting me about labels.
If I still have a question about /etc/fstab, i will post my fstab.
I don't know where to look to know that my boot loader is using uuid or dev. It would be great help.
Last edited by Archhotep (2013-03-25 16:06:11)

[SOLVED] Install arch on a partition and still access files on other

Basicaly what i want to achieve is to have a dual boot system on my laptop where i can access the files in some sort of shared storage or just to be able to access my windows files when im booted up in arch is there a way to achieve this?
Last edited by icyfox101 (2013-05-25 13:00:19)

Yes you can, you could have a partition for each OS, and then you could have a third partition for your shared files (I think it would have to be ntfs for the shared partition)
Or you could just mount the windows partition from arch.
https://wiki.archlinux.org/index.php/NTFS-3G

[Solved]Installed arch but got no internet

Hi!
I doesnt have any internet and my driver doesnt seem to auto load.
when typing ifconfig -a, eth0 doesnt show up, someone told me that the drivers wasnt loaded, and that I should use modprobe, but Im new and dont know what Im supposed to do.
Last edited by henningphan (2011-04-01 14:39:53)

lspci -v output
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
Subsystem: Acer Incorporated [ALI] Device 0487
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=0c <?>
Kernel driver in use: agpgart-intel
Kernel modules: intel-agp
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 02) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00003000-00003fff
Memory behind bridge: d0000000-d10fffff
Prefetchable memory behind bridge: 00000000a0000000-00000000b1ffffff
Capabilities: [88] Subsystem: Acer Incorporated [ALI] Device 0487
Capabilities: [80] Power Management version 3
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [a0] Express Root Port (Slot+), MSI 00
Capabilities: [100] Virtual Channel
Kernel driver in use: pcieport
Kernel modules: shpchp
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Device 0488
Flags: bus master, fast devsel, latency 0, IRQ 28
Memory at d1400000 (64-bit, non-prefetchable) [size=4M]
Memory at c0000000 (64-bit, prefetchable) [size=256M]
I/O ports at 4050 [size=8]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
Subsystem: Acer Incorporated [ALI] Device 0487
Flags: bus master, fast devsel, latency 0, IRQ 10
Memory at d5806100 (64-bit, non-prefetchable) [size=16]
Capabilities: [50] Power Management version 3
Capabilities: [8c] MSI: Enable- Count=1/1 Maskable- 64bit+
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) (prog-if 20 [EHCI])
Subsystem: Acer Incorporated [ALI] Device 0487
Flags: bus master, medium devsel, latency 0, IRQ 16
Memory at d5805c00 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci_hcd
Kernel modules: ehci-hcd
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
Subsystem: Acer Incorporated [ALI] Device 036d
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at d5800000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 00002000-00002fff
Memory behind bridge: d4800000-d57fffff
Prefetchable memory behind bridge: 00000000d1800000-00000000d27fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Acer Incorporated [ALI] Device 0487
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 00001000-00001fff
Memory behind bridge: d3800000-d47fffff
Prefetchable memory behind bridge: 00000000d2800000-00000000d37fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Acer Incorporated [ALI] Device 0487
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) (prog-if 20 [EHCI])
Subsystem: Acer Incorporated [ALI] Device 0487
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at d5805800 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci_hcd
Kernel modules: ehci-hcd
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=32
Capabilities: [50] Subsystem: Acer Incorporated [ALI] Device 0487
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)
Subsystem: Acer Incorporated [ALI] Device 0487
Flags: bus master, medium devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=10 <?>
Kernel modules: iTCO_wdt
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 05) (prog-if 01 [AHCI 1.0])
Subsystem: Acer Incorporated [ALI] Device 0487
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 27
I/O ports at 4048 [size=8]
I/O ports at 405c [size=4]
I/O ports at 4040 [size=8]
I/O ports at 4058 [size=4]
I/O ports at 4020 [size=32]
Memory at d5805000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [70] Power Management version 3
Capabilities: [a8] SATA HBA v1.0
Capabilities: [b0] PCI Advanced Features
Kernel driver in use: ahci
Kernel modules: ahci
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
Subsystem: Acer Incorporated [ALI] Device 0487
Flags: medium devsel, IRQ 19
Memory at d5806000 (64-bit, non-prefetchable) [size=256]
I/O ports at 4000 [size=32]
Kernel modules: i2c-i801
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05)
Subsystem: Acer Incorporated [ALI] Device 0487
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at d5804000 (64-bit, non-prefetchable) [size=4K]
Capabilities: [50] Power Management version 3
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
01:00.0 VGA compatible controller: nVidia Corporation Device 0df4 (rev a1) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Device 0488
Flags: fast devsel, IRQ 10
Memory at d0000000 (32-bit, non-prefetchable) [disabled] [size=16M]
Memory at a0000000 (64-bit, prefetchable) [disabled] [size=256M]
Memory at b0000000 (64-bit, prefetchable) [disabled] [size=32M]
I/O ports at 3000 [disabled] [size=128]
Expansion ROM at d1000000 [disabled] [size=512K]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Endpoint, MSI 00
Capabilities: [b4] Vendor Specific Information: Len=14 <?>
Capabilities: [100] Virtual Channel
Capabilities: [128] Power Budgeting <?>
Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
Kernel modules: nvidiafb
02:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe (rev 01)
Subsystem: Acer Incorporated [ALI] Device 036d
Flags: fast devsel, IRQ 16
Memory at d4800000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [48] Power Management version 3
Capabilities: [60] Vendor Specific Information: Len=6c <?>
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [cc] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 1c-75-08-ff-fe-9e-2d-93
Capabilities: [16c] Power Budgeting <?>
Kernel modules: tg3
03:00.0 Network controller: Broadcom Corporation Device 4357 (rev 01)
Subsystem: Foxconn International, Inc. Device e021
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at d3800000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information: Len=78 <?>
Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 00-00-6e-ff-ff-6c-4c-0f
Capabilities: [16c] Power Budgeting <?>
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
Subsystem: Acer Incorporated [ALI] Device 0487
Flags: bus master, fast devsel, latency 0
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
Subsystem: Acer Incorporated [ALI] Device 0487
Flags: bus master, fast devsel, latency 0
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
Subsystem: Acer Incorporated [ALI] Device 0487
Flags: bus master, fast devsel, latency 0
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
Subsystem: Acer Incorporated [ALI] Device 0487
Flags: bus master, fast devsel, latency 0
ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
Subsystem: Acer Incorporated [ALI] Device 0487
Flags: bus master, fast devsel, latency 0
ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
Subsystem: Acer Incorporated [ALI] Device 0487
Flags: bus master, fast devsel, latency 0
dmesg eth
eth%d: No PHY devices
dmesg eth
tg3.c:v3.106 (January 12, 2010)
tg3 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
tg3 0000:02:00.0: setting latency timer to 64
tg3 mdio bus: probed
tg3: Problem fetching invariants of chip, aborting.
tg3 0000:02:00.0: PCI INT A disabled
broadcom had no output
lsmod |grep tg3 had no output, so If I dont have tg3, how to get it?
Solved:
"modprobe tg3" //it helps me get eth0
than
"dhcpcd eth0" /to ask for an ip
problem solved, now I just need to find out why tg3 doesnt autoload or how to autoload it.
Last edited by henningphan (2011-04-01 14:39:37)

Problems after installing Arch [SOLVED]

Hello,
I attempted to follow the installation instructions to install Arch Linux. I followed those since they are faster than the Beginners Guide and didn’t meet some of my needs.
For example, I was also wanting to install an LVM partition (and I'll backup and set up dm-crypt+LUKS later after I get this issue solved), which the Beginner Guide didn't mention and there were a few other minor tweaks I wanted.
In my partition layout I have a 400MB boot (extra room for other kernels). followed by an LVM volume, which has one volume group with 4 logical partitions, these are: /, /home, /tmp, and /var.
The problem:
GRUB is not working, or at least it's not installed and configured correctly. When I boot up my computer, it says exactly, "GRUB", in the top-left corner of my screen and nothing happens. I have a poor understanding of the init/bootloader process in computers, which I am trying to learn slowly but steadily. I was re-reading the instructions for GPT specific partitions, which is what I use, and it says here:
http://www.gnu.org/software/grub/manual … stallation
That I'm supposed to have a "BIOS partition". This is interesting because I have no idea what this is for. Something came to mind when I was using cgdisk or gdisk, it would automatically allocate the first 2000-ish sectors (instead of 34 like the documentation was hinting), so this probably means something.... I don't know.
And then I read that the BIOS installation for GPT is supposed to be done before you install Arch Linux. Whoops! So can I fix this without having to reinstall Arch? I can probably mount all of my directories and chroot inside again after creating the BIOS partition so GRUB can be configured and reinstalled correctly. Maybe I can fix this. I don't know.
So I am trying to troubleshoot this problem, but is there anything I am understanding wrongly here? Is there some other reason why GRUB won't boot up? I tried Super GRUB 2 disk and that didn't work, there was just a blank screen when booting from grub.cfg. Any help or suggestions?
I am using x86_64 Arch Linux with the installed 3.6.4-1-ARCH Linux kernel.
Last edited by mrrhq (2012-11-08 22:31:49)

mrrhq wrote:In my partition layout I have a 400MB boot (extra room for other kernels). followed by an LVM volume, which has one volume group with 4 logical partitions, these are: /, /home, /tmp, and /var.
Be aware that logical partitions are a construct of the Master Boot Record (MBR) partitioning system; however, the title of your thread, and some of the specifics, suggest that you're using the GUID Partition Table (GPT) system, which doesn't use logical partitions. If you're certain you used gdisk or cgdisk, and not fdisk or cfdisk, then you're using GPT and I'd simply accept your use of the word "logical" as an error. If there's any doubt in your mind about this, though, you should investigate further, since some of the issues and solutions depend greatly on which partitioning system you used.
That I'm supposed to have a "BIOS partition". This is interesting because I have no idea what this is for.
The BIOS Boot Partition holds a portion of the GRUB code. It's used on GPT disks but not on MBR disks -- on MBR, the equivalent code goes in an officially-unallocated area immediately after the MBR. The BIOS Boot Partition can sometimes be just a few kibibytes in size, but it's usually either 1MiB or 2MiB. (I've seen reports that some configurations now require over 1MiB, but I haven't investigated this claim.)
Something came to mind when I was using cgdisk or gdisk, it would automatically allocate the first 2000-ish sectors (instead of 34 like the documentation was hinting), so this probably means something.... I don't know.
No, these are unrelated issues. Most partitioning tools today, including gdisk and its siblings, align all partitions on 2048-sector (1MiB) boundaries so as to avoid performance penalties that can be incurred on Advanced Format disks, SSDs, and some types of RAID arrays. See this article I wrote on the topic some time ago.
That said, if you have nowhere else to put it, you could try creating a BIOS Boot Partition in that space. You'd need to change the alignment policy in gdisk or cgdisk to align on 1-sector boundaries to do so, although an 8-sector alignment would be safer for future changes if you've got an Advanced Format disk. The BIOS Boot Partition isn't really greatly affected by the alignment issues, so I wouldn't worry about leaving it unaligned. OTOH, if GRUB wants more then 1MiB on your system, this space would be too small, so it might be better to resize a partition to make room for the BIOS Boot Partition.
WonderWoofy wrote:From what I understand (I have not tried this though) grub2 is actually lvm aware. So you can put all partitions within the lvm, including boot. If this is the case, I see no reason why you would not also be able to put the 2MB bios boot partition in there as well.
GRUB 2 is LVM-aware, and it is possible to put your Linux /boot directory inside the LVM. If you want to do this, though, there's really no point to split /boot off into a separate logical volume (the LVM equivalent of a partition); you might as well just make it a normal directory off of the root (/) filesystem. I'm pretty sure it is not possible to put the BIOS Boot Partition inside the LVM. That's because the code to parse the LVM data structures is contained within the BIOS Boot Partition, thus creating a chicken-and-egg situation if you were to attempt it. Furthermore, the code to write to the BIOS Boot Partition looks for the partition type code in the disk's partition table, and there's no equivalent to that in the LVM data structures. (All this said, in principle you might be able to get something like this to work, but the result would be something similar, but not identical, to a BIOS Boot Partition.)
Although GRUB 2 can read a kernel from within an LVM, I still prefer to keep a separate /boot partition. The reason is that you might not always use GRUB 2. If you wanted or needed to switch to another boot loader in the future, it might not be LVM-aware, and might need /boot to be on a true partition, not in an LVM. (This is true of every EFI boot loader except for GRUB 2, for instance.) In fact, I routinely create two or three smallish partitions on my computers so that I can create multiple /boot partitions for multi-boot configurations or to help transition to a new installation should the need arise. This can help simplify things when the time comes to start fresh.

[SOLVED] external USB HDD fails to install arch w/boot device ERROR

I've been working on installing arch linux via an external USB harddrive (specifically seagate free agent go 320GB) for 1 week now, and everytime I failed - until TODAY! thankfully I found this post, where user Dieter@be references this link, which displays BUG ID#17231 at the top titled "Can't boot LiveCDs 2009.08 (/dev/archiso doesn't show up)". the bug report states ::
I can't boot the LiveCDs 2009.08, neither netinstall nor core.
When it tries to access /dev/archiso it shows these messages:
:: Waiting for boot device ...
Waiting 30 seconds for device /dev/archiso ...
ERROR: boot device didn't show up after 30 seconds ...
Falling back to interactive prompt
You can try to fix the problem manually, logout when you are finished
ramfs$
reading further thru this bug report, I found a very insightful post by Heiko Baums (cyberpatrol) where he says the following, and I quote ::
Problem found. The link /dev/archiso wasn't created.
After
ramfs$ cd /dev
ramfs$ ln -s sr0 archiso
ramfs$ exit
it continued booting correctly.
And sg was also loaded after this. ;-)
as you see, the bug report was for the CD version, not the USB version - yet, my issue with the USB bootdisk was the same, (no matter which boot disk I tried = netinstall, core, .img, .iso, etc) meaning I got the EXACT same error = "ERROR: boot device didn't show up after 30 seconds ..." ! well, I figured that I'd try one of the new fancy ISOs found @ http://build.archlinux.org/isos/ - specifically I use/used archlinux-2010.03.04-netinstall-x86_64.iso.
upon running Unetbootin from windows 7, and choose to install the ISO archlinux-2010.03.04-netinstall-x86_64.iso to my first partition on my USB harddrive (that first partition being FAT32, and had already been set as bootable previously), that completed successfully. I rebooted, and choose to boot from USB drive, the ISOlinux bootloader came up as normal, I choose DEFAULT and off it went.... sure enough, it errored out at the same place as listed in the bug report ::
:: Waiting for boot device ...
Waiting 30 seconds for device /dev/archiso ...
ERROR: boot device didn't show up after 30 seconds ...
Falling back to interactive prompt
You can try to fix the problem manually, logout when you are finished
ramfs$
this time though, I issued the following 2 commands ::
ln -s /dev/sdb1 /dev/archiso
exit
from there, EVERYTHING worked as it should!
to recap: the solution for me was create a symbolic link pointing /dev/archiso => to my partition which held the archlinux netinstall (which is where I told Unetbootin to install it to)! done and done. I felt this needed to be posted here, as I could not find this solution after MANY google searches, archlinux wiki searches, forum searches, etc. honestly, I think it would be prudent to have this tidbit of information added to the Install from USB stick archwiki page as a side note to those that may run into this issue.
this is not the FIRST time I have run into this problem with a USB install of archlinux, but this is the FIRST time I found a fix! thanks to all the great posts I reference here, without this information I dont think I would have been able to install archlinux on my new alienware m11x laptop.
-peace-
PS: no amount of rootdelay=XX nor pmedia=usb nor usbdelay=XX would work in my above attempts either.
Last edited by fnord0 (2010-03-12 04:54:26)

FAT16 here. Parted Magic sees my USB drive as sdd. I tried your way and surprise, surprise, it didn't work.
ln -sf /dev/sdd /dev/archiso
mount -t vfat /dev/archiso /bootmnt
mount : Invalid argument
I thought maybe you meant mount -f vfat /dev/archiso /bootmnt instead. I tried it too, it resulted in a kernel panic.
What else can I try besides installing from a IDE/SATA CD drive ? Because this issue is NOT solved. At least not for me. Wonder if "archlinux-2010.04.05-netinstall-i686.iso" from the here will solve it (really hope so).
SOLVED IT HERE (with yet another image): http://bbs.archlinux.org/viewtopic.php?id=93645
Last edited by DSpider (2010-04-17 14:21:27)

[SOLVED] Help me install Arch on my W540

Hi guys,
I'm trying to install ArchLinux on my Lenovo W540. I've installed Arch on so many other Notebooks and desktop computers before but they all had a non UEFI Bios. This one is a bit tricky.
I dd'ed the arch iso on my usb and booted it up.
The result is a freeze during booting from the usb: http://i.imgur.com/hUMT36E.jpg
Can anyone help me install Arch on my W540? Or tell me what the problem is?
Thanks in advance
--lmnsqshr
Last edited by lmnsqshr (2014-10-29 20:37:33)

Ok, I got a solution but this will probably piss off some people googling for "how to install Arch Linux on Lenovo W540" because it's not a reproducable solution (sorry).
TL;DR: USB flash drive was corrupt.
After booting from the USB, I changed the boot parameters of the x86_64 entry and added a "nomodeset". This would prevent the graphical drivers from loading, because the problem was apparantly with the nouveau-module.
The live system booted and I got to the point where I partitioned my SSD. The command "mkfs.ext4 /dev/sda1" got me some I/O errors so I thought the USB flash drive might be corrupted (it was pretty old).
I dd'ed the arch iso on a new USB flash drive which somehow could load the nouveau module without any problems. And now I'm running my beloved Arch on my W540.
/EDIT: I just remembered that I also disabled the integrated card reader in the BIOS.
Last edited by lmnsqshr (2014-10-29 20:49:01)

[SOLVED] BIOS not detecting USB Drives after i installed Arch

SOLVED: In BIOS under 'Advanced' disable 'Fast BIOS Mode'.
Original post:
Hi there!
I'm fairly new to the arch (and linux) scene and just setup my Samsung 530U3B with a brand new installation of arch. Everything went fine and the system is running flawlessly. Almost.
I just happend to notice that BIOS is not checking for USB drives anymore, it just somehow skips that part. If enter the boot selection, the bootable USB drive won't show up. Neither does it show up in BIOS setup. I tried to boot with the same USB drive that i used to install arch just yesterday, the live media does not boot - the drive doesn't even blink. The boot priority is set to usb drive first, the boot selection screen (hammering f10 during boot) doesn't give me any other option than to boot from the normal SSD. Also, prior to the arch installation (came with w7 installed) the BIOS screen would stay for about 2seconds and then proceed to boot - this doesn't happen anymore. When i press the power button greeted by the grub bootloader in about 1s.
I tried 2 different usb drives, both with the arch iso (same that i used to install the currently running OS, downloaded yesterday). The drives also show up once my arch is booted (starting to blink just after i hit enter in grub). Also, both drives boot without a problem on my desktop computer.
Anyone got any ideas?
I don't really now what kinda of information would be helpful so i'm just dumping stuff i know:
BIOS: Phoenix SecureCore Tiano Version 04XK
Machine: Samsung 530U3B
SSD: Samsung MZ7PC128HAFU-000
ISO used to install (checksum ok): archlinux-2012.07.15-netinstall-dual.iso
Last edited by araex (2012-07-26 16:57:47)

DSpider wrote:
The boot priority is set to usb drive first
Welcome to the forum.
If you just set the USB stick to be first in the boot order, the next option (from the list) takes its place the moment you unplug it. You need to set the BIOS to boot from your equivalent of "Removable Devices" first, "Internal Drives" second and "Optical Drives" third.
The USB stick doesn't show up at all. I set the priority as follows:
1. USB HDD
2. USB FDD
3. USB CD
4. SATA CD
5. SATA HDD
6. NETWORK
I used that same configuration to install arch. USB doesn't seem to initialize at all. Also, if i enter "usb" in the grub commandline, no devices are listed.
Thanks!
UPDATE:
I just figured it out. In my BIOS under 'Advanced' the 'Fast BIOS Mode' was enabled, once i disabled it, everything went fine. I don't remember changing that option. Silly me.
Sorry for your time
Last edited by araex (2012-07-26 16:56:30)

[Solved] Installing arch on a notebook /w a 2.6.33+ chipset

Similar Messages

Maybe you are looking for