The main thing that seems wrong here is that in the line
kernel /vmlinuz26 root=/dev/disk/by-uuid/2a53bdc8-7a9a-4dd2-9aef-5b7b4c3e74a4 ro vga=775
You are using the uuid for /dev/sdc3
which is your /home
partition, you should be using the uuid for /dev/sdc2
which is your /
partition.
Also... the output from sudo blkid
does not match what is shown in fstab
. In blkid the swap partition is /dev/sdc2
, but in fstab the swap partition is /dev/sdc4
...
You need to figure out these descrepencies.... then you can try to re-configure your grub.conf
Some pointers:
Have you tried other values of root, like root (hd2,1)
?
Instead of
kernel /vmlinuz26 root=/dev/disk/by-uuid/2a53bdc8-7a9a-4dd2-9aef-5b7b4c3e74a4 ro vga=775`
you could try things like
kernel /vmlinuz26 root=/dev/sdc2 ro vga=775
Make sure that /boot/kernel26.img
exists.
From the live CD
You seem to be able to get a working connection on the installation media, so here is one idea: Start the arch live CD and setup your network. Then mount your newly installed partition (for example on /mnt
) and chroot
into your system using
# arch-chroot /mnt
From there, you will be able to update pacman
's database and install the desired packages. For broadcom, you will need to install from AUR:
# pacman -Syy base-devel
# pacman -S b43-fwcutter
# curl https://aur.archlinux.org/cgit/aur.git/snapshot/b43-firmware.tar.gz | tar xzf -
# cd b43-firmware
# makepkg --asroot --install
Note: never use --asroot
in normal situation.
Without network connection
This is a little bit more tricky here. Compiling from AUR will be harder, so if you can first setup the ethernet using official packages, that will be better. The idea is to let pacman
prepare a list of downloads, use another PC and a USB stick to convey the packets to your install. Mount the USB stick on your fresh install and create a list of packages to download.
# cd /mnt/usbstick
# pacman -Sp your_ethernet_driver > pkgs_list.txt
If you really want to install the broadcom drivers (or your ethernet card is also an unofficial packet) also issue
# pacman -Sp base-devel b43-fwcutter >> pkgs_list.txt
Unmount the key and find an internet connection on another PC. Download all the packets using for example curl
, wget
or simply your browser. If you are really unlucky, the pacman database may be too old and you will not find the packets in their indicated version. You will have to search a little bit round to find the right package. Save all the packets on the stick.
If you go the unofficial way, find the page on the AUR and download the tarball for the packet, but also all dependencies and all sources. For broadcom, for example download the b43-firmware
tarball but also the http://www.lwfinger.com/b43-firmware/broadcom-wl-{xyz}.tar.bz2
source tarball.
Go back to your arch and from your stick run
# pacman -U *.pkg.tar.*
For broadcom, (or similar for unofficial packets)
# tar xzf b43-firmware.tar.gz
# cd b43-firmware/
# mv ../broadcom-wl-{xyz}.tar.bz2 .
# makepkg --asroot --install
Note: the third step moves the sources into the build directory so that makepkg finds it locally and do not attempt to download them. And same, do not use --asroot
in normal case.
Best Answer
In general: This feature allows the kernel to replace the remapping tables created by your BIOS.
If it's a system firmware bug, updates to Arch aren't going to fix it. You'd need to update your system firmware (BIOS/UEFI) by flashing. I personally don't recommend that. You should only do this if you really know how to flash your hardware.
The "soft" way is to disable the interrupt remapping in the kernel boot parameters.
intremap=off
disables the kernel interrupt remapping, which might point to your buggy bios or hardware.First take a look at your config with
cat /proc/cmdline
. Copy it to see changes later on. Now back up your/etc/default/grub
by copying it to a direction you want. To make the change persistent after a reboot edit/etc/default/grub
and append your kernel options to theGRUB_CMDLINE_LINUX_DEFAULT
line. In your case it isintremap=off
(put it into the " "). You can delete thequiet
if it is in there. Save it and exit.Now re-generate the grub.cfg file (it is generated with the parameters written in
/etc/default/grub
) with:sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Reboot your system and the error should be gone. Take a look at your config with
cat /proc/cmdline
, your changes should be visable.