Actually I don't use CONFIG_DEVFS_FS as it tends to break things here
(and I found wasn't necessary for things to work, in fact it got in the
way of some things working, some of the autodetect/hotplug peripherels
didn't like it). Thank you for the reply though.
Bob
On Mon, 2005-04-04 at 20:14
Actually I don't use CONFIG_DEVFS_FS as it tends to break things here
(and I found wasn't necessary for things to work, in fact it got in the
way of some things working, some of the autodetect/hotplug peripherels
didn't like it). Thank you for the reply though.
Bob
On Mon, 2005-04-04 at 20:14
On Mon, Apr 04, 2005 at 08:22:56PM -0600, Bob Gill wrote:
> Hi. I recently built 2.6.12-rc1-bk6. The kernel seems to be tripping
> over sbp2. The error messages keep right on rolling till I hit the
> reboot button (I let it run for more than 90 seconds last time).
> 2.6.11.6 builds/runs without
Hi. I recently built 2.6.12-rc1-bk6. The kernel seems to be tripping
over sbp2. The error messages keep right on rolling till I hit the
reboot button (I let it run for more than 90 seconds last time).
2.6.11.6 builds/runs without any problems.
My build scripts includes:
# IEEE 1394 (FireWire)
Hi. I recently built 2.6.12-rc1-bk6. The kernel seems to be tripping
over sbp2. The error messages keep right on rolling till I hit the
reboot button (I let it run for more than 90 seconds last time).
2.6.11.6 builds/runs without any problems.
My build scripts includes:
# IEEE 1394 (FireWire)
On Mon, Apr 04, 2005 at 08:22:56PM -0600, Bob Gill wrote:
Hi. I recently built 2.6.12-rc1-bk6. The kernel seems to be tripping
over sbp2. The error messages keep right on rolling till I hit the
reboot button (I let it run for more than 90 seconds last time).
2.6.11.6 builds/runs without any
6 matches
Mail list logo