Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 110438 - during installation [ x86_64 ]; after load vmlinuz; get error- cannot mount cdrom
Summary: during installation [ x86_64 ]; after load vmlinuz; get error- cannot mount c...
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Release Media
Classification: Unclassified
Component: Everything (show other bugs)
Hardware: AMD64 Linux
: High major (vote)
Assignee: Gentoo Release Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-25 07:05 UTC by Andrey
Modified: 2006-07-19 05:47 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey 2005-10-25 07:05:28 UTC
during installation [ x86_64 ]; after load vmlinuz; get error- cannot mount 
cdrom; as a result unable to install gentoo linix on this hardware platform; HW 
specs:  x86_64; dual xeon 2.8 ; intel server board SR1435VP2

Reproducible: Always
Steps to Reproduce:
1. load vmlinuz 
2. get error - cannot mount cdrom
3. x86_64; dual xeon 2.8 ; intel server board SR1435VP2

Actual Results:  
get error - cannot mount cdrom

Expected Results:  
able to mount cdrom and start the installation

x86_64; dual xeon 2.8 ; intel server board SR1435VP2
Comment 1 Chris Gianelloni (RETIRED) gentoo-dev 2005-10-25 07:08:58 UTC
This has nothing to do with the Installer project.

Those *are* EM64T Xeons, correct?  Also, exactly which CD are you using?
Comment 2 Andrey 2005-10-25 08:04:36 UTC
Please see inline:

>Those *are* EM64T Xeons, correct?  Also, exactly which CD are you using?
Yes, we are using EM64T Xeons. The CD image is located:
http://bouncer.gentoo.org/?product=gentoo-2005.1-install-universal&os=amd64

Thank you,
Andrey
Comment 3 Chris Gianelloni (RETIRED) gentoo-dev 2006-03-15 06:09:56 UTC
Can you try 2006.0 and see if the problem is resolved?
Comment 4 Chris Gianelloni (RETIRED) gentoo-dev 2006-07-19 05:47:33 UTC
No reponse.  Likely fixed with 2006.0's release.  Feel free to REOPEN the bug if it was not fixed and you have time to assist in testing this.