Hello,
Where I've had no trouble building 2.2.x kernels (up through 2.2.16)
that work well on my Compaq Presario 1250 laptop, I've been having
trouble with the latest development kernels. If it's of any
relevance, the machine has an AMD K6-2 300MHz processor, 96MB of RAM,
and no plug-n-pray that I can find.
I'm afraid to burden you all with all 790 lines of my latest .config
file, but if you could point me at the right things to check, I'd
appreciate it. But the obvious ones:
CONFIG_HOTPLUG=y
# PCMCIA/CardBus support
CONFIG_PCMCIA=y
# PCMCIA network device support
CONFIG_NET_PCMCIA=y
CONFIG_PCMCIA_3C589=m
CONFIG_PCMCIA_3C574=m
CONFIG_PCMCIA_FMVJ18X=m
CONFIG_PCMCIA_PCNET=m
CONFIG_PCMCIA_NMCLAN=m
CONFIG_PCMCIA_SMC91C92=m
CONFIG_PCMCIA_XIRC2PS=m
CONFIG_PCMCIA_IBMTR=m
CONFIG_PCMCIA_XIRTULIP=m
# CONFIG_NET_PCMCIA_RADIO is not set
CONFIG_PCMCIA_SERIAL=y
# PCMCIA character device support
# CONFIG_PCMCIA_SERIAL_CS is not set
# CONFIG_PCMCIA_SERIAL_CB is not set
CONFIG_SOUND=y
# CONFIG_SOUND_CMPCI is not set
# CONFIG_SOUND_EMU10K1 is not set
# CONFIG_SOUND_ES1370 is not set
# CONFIG_SOUND_ES1371 is not set
# CONFIG_SOUND_ESSSOLO1 is not set
# CONFIG_SOUND_MAESTRO is not set
# CONFIG_SOUND_SONICVIBES is not set
# CONFIG_SOUND_TRIDENT is not set
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
# CONFIG_SOUND_VIA82CXXX is not set
CONFIG_SOUND_OSS=m
CONFIG_SOUND_TRACEINIT=y
CONFIG_SOUND_DMAP=y
# CONFIG_SOUND_SGALAXY is not set
# CONFIG_SOUND_ADLIB is not set
# CONFIG_SOUND_ACI_MIXER is not set
# CONFIG_SOUND_CS4232 is not set
CONFIG_SOUND_SSCAPE=m
# CONFIG_SOUND_GUS is not set
# CONFIG_SOUND_ICH is not set
# CONFIG_SOUND_VMIDI is not set
# CONFIG_SOUND_TRIX is not set
# CONFIG_SOUND_MSS is not set
# CONFIG_SOUND_MPU401 is not set
# CONFIG_SOUND_NM256 is not set
# CONFIG_SOUND_MAD16 is not set
# CONFIG_SOUND_PAS is not set
# CONFIG_SOUND_PSS is not set
# CONFIG_SOUND_SOFTOSS is not set
CONFIG_SOUND_SB=m
# CONFIG_SOUND_AWE32_SYNTH is not set
# CONFIG_SOUND_WAVEFRONT is not set
# CONFIG_SOUND_MAUI is not set
# CONFIG_SOUND_YM3812 is not set
# CONFIG_SOUND_OPL3SA1 is not set
# CONFIG_SOUND_OPL3SA2 is not set
# CONFIG_SOUND_YMPCI is not set
# CONFIG_SOUND_UART6850 is not set
# CONFIG_SOUND_AEDSP16 is not set
# CONFIG_SOUND_TVMIXER is not set
Neither PCMCIA nor sound is working. PCMCIA modules fail to load; the
whole process fails to create the pcmcia directory I'm used to seeing.
I see the source for the 3C575 driver in the pcmcia-cs directory; it
doesn't seem to be getting drawn in with the installation.
The ESS1869 sound chip on this machine is no longer recognized even
though I'm using the same configuration options I did with the 2.2.x
kernels.
Also, any attempt to reboot this kernel creates a condition where the
console display is garbled and ceases to display anything after where
it's saying (I think) decompressing the kernel.
Reviewing /var/log/messages after picking up the pieces later, I see:
Jun 13 20:31:57 area66-1 mingetty[271]: /dev/tty1: cannot open tty: No
such device
Jun 13 20:31:57 area66-1 mingetty[272]: /dev/tty2: cannot open tty: No
such device
Jun 13 20:31:57 area66-1 mingetty[282]: /dev/tty1: cannot open tty: No
such device
Jun 13 20:31:57 area66-1 mingetty[274]: /dev/tty4: cannot open tty: No
such device
Jun 13 20:31:57 area66-1 mingetty[273]: /dev/tty3: cannot open tty: No
such device
Jun 13 20:31:57 area66-1 mingetty[275]: /dev/tty5: cannot open tty: No
such device
Jun 13 20:31:57 area66-1 mingetty[293]: /dev/tty5: cannot open tty: No
such device
Jun 13 20:31:58 area66-1 mingetty[291]: /dev/tty3: cannot open tty: No
such device
Jun 13 20:31:58 area66-1 mingetty[289]: /dev/tty4: cannot open tty: No
such device
Jun 13 20:31:58 area66-1 mingetty[299]: /dev/tty4: cannot open tty: No
such device
Jun 13 20:31:58 area66-1 mingetty[297]: /dev/tty3: cannot open tty: No
such device
Jun 13 20:31:58 area66-1 mingetty[295]: /dev/tty5: cannot open tty: No
such device
Jun 13 20:31:58 area66-1 mingetty[286]: /dev/tty1: cannot open tty: No
such device
Jun 13 20:31:58 area66-1 mingetty[307]: /dev/tty1: cannot open tty: No
such device
Jun 13 20:31:58 area66-1 mingetty[305]: /dev/tty5: cannot open tty: No
such device
Jun 13 20:31:58 area66-1 mingetty[303]: /dev/tty3: cannot open tty: No
such device
Jun 13 20:31:58 area66-1 mingetty[301]: /dev/tty4: cannot open tty: No
such device
Jun 13 20:31:58 area66-1 mingetty[283]: /dev/tty2: cannot open tty: No
such device
Jun 13 20:31:58 area66-1 mingetty[276]: /dev/tty6: cannot open tty: No
such device
Jun 13 20:31:58 area66-1 mingetty[319]: /dev/tty6: cannot open tty: No
such device
It goes on like this for a while. To successfully reboot, I must
power off the system. It will then come up cleanly under my stable
kernel.
I've been observing these problems since about 2.3.49. I gave up
building development kernels until 2.3.99. Now I'm afraid I won't be
able to get 2.4.0 up when you actually release it. I figure I must be
doing something wrong, and have been trying to watch for someone else
having these problems -- but I ain't seen it yet.
So, with apologies for troubling you with my own ineptitude, I feel
compelled to ask what it is I could be doing wrong?
Thanks.
--
David Benfell
benfell@greybeard95a.com
ICQ 59438240 [e-mail first for access]
---
There are no physicists in the hottest parts of hell, because the
existence of a "hottest part" implies a temperature difference, and
any marginally competent physicist would immediately use this to
run a heat engine and make some other part of hell comfortably cool.
This is obviously impossible.
-- Richard Davisson
[from fortune]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jun 15 2000 - 21:00:30 EST