Bug#403794: Package: base Debian ETCH will not recognize the CD-ROM

[Art Blackwell]

Interesting response. 

The failure I was referring to was what happened AFTER I did a NETWORK download and install of the LATEST daily. That is the state that the Proliant 3000 was left in. No access to fd0 and cdrom. It couldn't even " see " the package ( on CD ) that started the install in the first place! I had to remove the repository to get the system upgrades!
I report what I see. The system won't boot ETCH and mount fd0 and cdrom. It will boot and run SARGE with no problems. It will boot and run W2000AS with no problems. DEV entries for fd0 and cdrom are missing in ETCH after the network upgrades.

On the eye candy. I have always used the TEXT install. That avoids problems with graphics cards and using any X installations. That is a holdover from my UNIX days when X was difficult to configure and get right.

[rant]
The bottom line: I guess the DEBIAN community has really not changed it's attitude over the YEARS  if your post is an
 example of what I can expect in terms of help. I went out of my way to DIAGNOSE a problem and ask about help in resolving it. I do HARDWARE real well, not SOFTWARE. The creation of the X-MP and Y-MP systems are good examples of that. I cut my teeth on UNIX SVR4 and remember what a nightmare it was to get X running.
 I have FOUR Proliant systems which are used as PERSONAL systems. That gives me time to play with different distros and look at the + and - of each.
The GENERAL community looks at DEBIAN as a PITA to configure and point to it as an example as to why M$ products are better. Is that the attitude you want DEBIAN to maintain?
 Mark S. has created what appears to be a POLISHED DEBIAN based " product "  THAT WORKS WELL OUT OF THE BOX!!
UBUNTU even offers a working implementation of Edgy Eft for a COMPAQ server!
ETCH had a problem and I thought I could help out. ( There are many PROLIANT 3000 systems still out in the SERVER world ) I guess
 I was mistaken.
I resolved my problem by installing KUBUNTU/UBUNTU Server packages. The best of BOTH worlds. High level  tools to get the job done. Now on to CLUSTERKNOPPIX and some SUPERCOMPUTER design....
 You can close this bug report out if you wish, but from MY viewpoint, there are SEVERAL problems that need to be addressed. I suggest that this rant be kicked up to the people  who complained about PAYING people to " finish " a DEBIAN " product ". 
[/rant]

Sincerely Yours,

Arthur Blackwell




Frans Pop <elendil@xxxxxxxxx> wrote:
>  On Sunday 24 December 2006 09:41, Amaya wrote:
> > The good news: NICE eye candy compared to the usual install!
>
> Huh? I guess you must be referring to the graphical installer, but that 
> was also available in the original image you tried and never
>  booted by 
> default.
> Did you in fact boot the image differently?
>
> In your initial report, I'm a bit confused if you are talking about 
> missing CD support during an install or after reboot into the installed 
> system. I'm assuming installation.
>
> In your initial report you said: no CD drives _after_ network config, but 
> when installing from CD, the CD detection always happens _before_ network 
> config. Please follow the installation procedure and report what happens 
> accurately.
>
> > The bad news: I have the same problem: no recognition of the floppy or
> > CD-ROM drives. The /DEV directory entries needed are still missing, and
> > the drives won't mount.
>
> To be of any help, we'll need at least the output of 'lspci -nn' for that 
> box.
>
> Also, please try the diagnostics suggested at:
> http://d-i.alioth.debian.org/manual/en.i386/ch05s01.html
> and report your findings.
>
> Another option to try is to install in
>  expert mode (boot with 'expert') 
> and only selectively load modules needed to detect the CDROM at first.
>
> Note that the issues you are seeing are almost always due to driver 
> conflicts in the kernel, and not problems in the installer itself. We can 
> only suggest things to try and, if we do manage to identify an issue, 
> forward it to kernel maintainers. There is very little chance we can 
>
> As you also have working images from other distros, the best chance of 
> identifying what is up is if you investigate this yourself: what kernel 
> versions are used, what modules are loaded and in what order. Are there 
> relevant differences that could make one work and the other not. Try 
> things manually.
>
> If are in a hurry to install the box, you could also try netbooting the 
> box instead of installing from CD.
>
> Cheers,
> FJP



" Those who do not learn from the past are doomed to repeat it " - Santayana

I
 hold to the FATALIST PORCINE philosophy of life:

 " I PINK, therefore I HAM "

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com