![]() You're perfectly free to -Syu all you like, no need to hold anything back. Once setup, am I free to 'pacman -Syu' once in a while, or are there any packages I must hold off from updating (the kernel especially)? No need to play around in chroot unless one wants to. I also included dialog to make use of the wifi-menu, so one can just simply extract it and boot. Mine has kernel for N900 and my integration packages included. What is the difference between the official rootfs, and the one provided by Skry? Is the unofficial just fine tuned towards the N900? Yeah, I've spent countless nights with this one, you're welcome. I'm quite interested in trying this, especially seeing as you, Skry, and many others have put in a lot of effort, thanks a lot, since the last time I looked at this project a long time back. I think I'm missing some part of U-boot boot, but I don't know what is it :( NOTE: when Kernel Panic happens, N900 can't be powered off using power button, you have to remove the battery which is bad :(Īnd also chroot worked fine, I tried doing pacman -Suy and it worked Kernel Panic - not syncing: VFS: Unable to mount rootfs on unknown-block(179,5)ītw : I tried multiple versions of u-boot with no luck I did the fixes you told me to do, But when you boot to Arch Good luck.īut init=/bin/systemd was right, (writing mistake :) ) You don't need to copy uImage anywhere if you configure uboot to look under /boot for it, like you've already done. Let me know if some issues arise.Īndinit=/bin /systemd -> init=/bin/systemd Oh well, setting up everything in fstab drops to emergency mode, module dependencies have to be defined manually, I'll get back to this asap.Ĭorrected and updated, update your fstab and do trough the steps again. ![]() I'm dead tired, so don't copypaste, I didn't :P I tried to reproduce all the stupid user errors I've heard happening with u-boot, so far it's been working fine and safe, for me. Ln -s /mnt/maemo/etc/default/em /etc/default/em Ln -s /mnt/maemo/etc/bootmenu.d /etc/bootmenu.d dev/mmcblk1p1 /mnt/maemo/home/user/MyDocs vfat defaults,noatime,uid=1000,gid=100,umask=022 0 0Īs root, emmc and nand partitions unmounted:Įcho "options ubi mtd=rootfs" > /etc/modprobe.d/ubi.confĮcho "softdep ubi pre: omap2" > /etc/modprobe.d/ubi.conf dev/mmcblk1p2 /mnt/maemo/home ext3 defaults,noatime 0 0 Ubi0:rootfs /mnt/maemo ubifs defaults,noatime,bulk_read,no_chk_data_crc 0 0 Changed behavior presented in here () for the interested. I'd appreciate any insight/help with this matter.Ok, uboot-n900-tools in the repo. If there I any more info needed, please let me know. I've reproduced this once now, with a clean install of Arch, and gnome. When I run sudo startx, There is no error displayed, and 3 terminal windows (with a Windows 98 looking teal UI) and a cursor appear, that's it. I have installed xorg, xinit, and all related/required libraries afaik. When installing xorg, I selected the nvidia-340.xx driver to be installed. Modprobe: FATAL: Module nvidia not found.Īs you probably gathered from the error, I am running an NVIDIA GPU, specifically the GTX 980. Xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) When I hit enter, I am returned to the terminal where the following error is displayed. When I run startx, I am brought to a white "Oh no, something has gone wrong." screen (no cursor). I'm running into some roadblocks in getting GNOME to run though. I just got through my first installation of glorious Arch Linux on my main, desktop PC.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |