You are not logged in.
So here's the context I know, please bear with me:
I've downloaded and burned the _64 net inst to CD some hours ago. Installed successfully to the virtualBox I have on my OSX/macbookpro5,3. Success.
Then I partitioned my disk, and tried to install onto the hardware directly. The CD start menu comes up, and I of course select the 1st option.
Two concerns come up:
1) I get a error that Address Space Collision of the Host Bridge Window and the video ROM as like the second line, and quickly scrolls off.
I get about two screen's worth of successful module loading. And then then the line advertising archlinux.org, then the start of boot itself.
In boot sequence, I get the only as far as the UDev until it hard hangs (4x PRAMIN flush timeout). Need to press Power button, try again.
2) nouveau hates my laptop:
Mounting Root Read Only
Adjusting system time and setting kernel time zone
Starting Udev Daemon
Trigger UDev uevents
Waiting for Udev uevents to be processed
[49.587439] [drm] nouveau 0000:02:00.0: dcb I2c entry invalid
[49.793332] [drm] nouveau 0000:02:00.0: PRAMIN flush timeout
[52.021320] [drm] nouveau 0000:02:00.0: PRAMIN flush timeout
[53.698469] [drm] nouveau 0000:02:00.0: PRAMIN flush timeout
[55.319998] [drm] nouveau 0000:02:00.0: PRAMIN flush timeoutI tried some minor suggestions for other video concerns and nothing has made any difference so far.
Now I've looked up both of these found a folks who've had these issues but still continue their boot processes-- then again, they are booting installed systems.
I'm unsure if these are connected, and am hoping that it doesn't have anything to do with my lappy's EFI.
One guy was able to 'blacklist' the nouveau module so it wouldn't explode all over place, but again-- his was already installed on disk. I'm not sure which manual would explain such a fancy pants file-in-RAM kind of editing for installation purposes. But would that fix the first issue?
At the end of the day, It's not clear to my that the Nouveau shennanigans isn't a symptom of my earlier overlapping video regions, but I don't see how.
So I'm not sure what the next step is, except to post it here and hope for the best. Am I just SOL until 'upsteam' fixes the mess?
Thank you for your time.
Last edited by incaramos (2012-03-05 22:01:40)
Offline
When the CD start menu comes up and you select the version you need (i386 or x86_64), strike TAB instead of ENTER.
There will be a console command line presented to you. Just add " nomodeset" to the command and strike ENTER.
Mind the whitespace (spacebar) and you can continue your installation journey.
Last edited by helonaut (2012-03-05 09:54:25)
Offline
Fantastic! Thank you.
Offline
Glad it worked out.
Chances are that you will run into this problem again when rebooting after finishing a successful installation, because your bootloader (probably Grub) by default will cause the same problem to arise.
To overcome this, you could edit the grub menu file as root (nano /boot/grub/menu.ls) after booting into installation disc and selecting root (cd /).
There will be two (probably identical) lines to edit (default & fallback): "kernel (...) ro"
Same deal here to fix the boot problem: add " nomodeset" behind these lines and strike CTRL + X to save the file.
When up and running you could check out the nvidia closed drivers or keep the nouveau drivers with this quick fix.
Offline