I wanted to try sarge by swapping out my main hard drive and putting in
a spare 10GB drive just to see how it's like. Installation was easy
(despite my need for manually configure network settings) and base installation went fine, but...
Rebooting didn't finish. The kernel booted, but after a while I just got
my monitor shut off, and trying to switch between consoles didn't help.
ctrl-alt-del initiated reboot sequence so I didn't need to do a cold
boot, but that was it. The same results were had in the "recovery"-mode.
I guess the installation of other packages (besides the base system)
should have started (?), but I have no idea what happened after the
screen went blank.
I have a Radeon 9600XT graphics adapter, which might be the cause of incompabilities, ie. framebuffer driver crashing the display or
XFree86's radeon-driver doing the same. Though does Debian use fb and
does the XFree86 even start at that time (first boot after base install)?
The last messages I see when booting are:
1) various USB messages (over one full screen of them)
2) just before monitor shutting itself, something about
"xxxx
net
pci" or something like that... hotplug things? Those are shown only
for a fraction of a second, after the USB messages, before the monitor
goes off.
It seems that most of the failures people are getting installing rc1 are because hotplug loads unsafe kernel modules, including hardware
watchdogs, and frame buffer modules that don't work right. It doesn't
help that as you noticed hotplug brings in all these unnecessary modules
even in single user mode.
Your problem sounds like hotplug loading a bad frame buffer module. Try booting in emergency mode ("linux emergency"), remount the root
filesystem read-write ("mount -o remount,rw /"), remove /etc/rcS.d/S40hotplug, then you should be able to boot without this
problem. If you can send us your lspci and lspci -n output, we can
probably determine which module hotplug is loading to cause your
problem, and fix it.
On Tuesday 10 August 2004 22:52, Joey Hess wrote:Maybe, but the default configuration will not load any module for the
Your problem sounds like hotplug loading a bad frame buffer module. Try
Maybe, but the default configuration will not load any module for the
display PCI class.
If you want to help finding which module breaks your system please
run *AS A USER* "/etc/hotplug/pci.rc start", it should display which
modules are going to be loaded (and fail loading them, because you are
not root). Then try to manually load each of them with modprobe and
report which one crashes your system.
Marco d'Itri wrote:I don't know... Fumitoshi UKAI worked on this. Please attach your /etc/default/hotplug file, it should contain IGNORE_PCI_CLASS_DISPLAY=true.
Maybe, but the default configuration will not load any module for the display PCI class.I know that's not true, because hotplug on fresh d-i installs has taken
to loading the matroxfb module for my test laptop, which yields a very
nice highres console. And when I disable hotplug, it stops being loaded. Maybe you have a bug?
Marco d'Itri wrote:I don't know... Fumitoshi UKAI worked on this. Please attach your /etc/default/hotplug file, it should contain IGNORE_PCI_CLASS_DISPLAY=true.
Maybe, but the default configuration will not load any module for the display PCI class.I know that's not true, because hotplug on fresh d-i installs has taken
to loading the matroxfb module for my test laptop, which yields a very
nice highres console. And when I disable hotplug, it stops being loaded. Maybe you have a bug?
If you want to help finding which module breaks your system please
run *AS A USER* "/etc/hotplug/pci.rc start", it should display which
modules are going to be loaded (and fail loading them, because you are
not root). Then try to manually load each of them with modprobe and
report which one crashes your system.
retitle 264870 radeonfb breaks the system
thanks
Turned out to be that IGNORE_PCI_CLASS_DISPLAY doesn't work, and loading rivafb was the problem. Installing 0.0.20040329-14 from unstable fixedSo the bug with $IGNORE_PCI_CLASS_DISPLAY and 2.4 kernels is fixed in
the problem.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 47:40:06 |
| Calls: | 12,112 |
| Calls today: | 3 |
| Files: | 15,010 |
| Messages: | 6,518,503 |