(In reply to comment #24)
> This is only an issue for upgrades from woody; on a fresh install,
> it will use hdc consistently.
About that: I've been struggling with getting a fresh install to work on a very
similar blue/white G3. Others have had similar experiences. Please see http://www.ubuntuforums.org/showthread.php?t=8050 for further discussion. I've
contributed to the discussion there as Random Juju.
The relevant part of that discussion is that I've modified the loadmodules file
as suggested here, but am still unable to boot. Booting with the modified
initrd.img yields:
[tux logo]
PCI: Cannot allocate resource region 0 of device 0000:01:02.0
audit(1104724407.122:0): initialized
mount: mount point proc does not exist
cat: proc/sys/kernel/real-root-dev: No such file or directory
/linuxrc: 9: cannot create proc/sys/kernel/real-root-dev: Directory nonexistent
Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
I don't know if this is a symptom of the same problem, but it seems that it may
be causing further problems with fresh installs.
(In reply to comment #24)
> This is only an issue for upgrades from woody; on a fresh install,
> it will use hdc consistently.
About that: I've been struggling with getting a fresh install to work on a very www.ubuntuforum s.org/showthrea d.php?t= 8050 for further discussion. I've
similar blue/white G3. Others have had similar experiences. Please see
http://
contributed to the discussion there as Random Juju.
The relevant part of that discussion is that I've modified the loadmodules file
as suggested here, but am still unable to boot. Booting with the modified
initrd.img yields:
[tux logo] 7.122:0) : initialized kernel/ real-root- dev: No such file or directory kernel/ real-root- dev: Directory nonexistent
PCI: Cannot allocate resource region 0 of device 0000:01:02.0
audit(110472440
mount: mount point proc does not exist
cat: proc/sys/
/linuxrc: 9: cannot create proc/sys/
Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
I don't know if this is a symptom of the same problem, but it seems that it may
be causing further problems with fresh installs.