Hi there,

I googled a bit to find a solution to my problem. It seems, however,
that no-one ever mentioned something alike. My current configuration is:
AMD 2400+, 512 MB RAM, AsRock motherboard. Currently using Windows 2000.
I've purchased Slackware 10.0 distribution today (I used to use 8.1 for
quite a long time and really fancied it) as to install it on the
remaining partition. But the installation process halts as soon as
welcome screen is displayed. I have a prompt "boot:" but also all three
lamps on my keyboard are lit and there's no responce to my hitting all
keys... What is screwed up? Is it BIOS or my configuration the Slackware
dislike? I am in despair. Help. :-)

Any tips and recommendations are deeply appreciated. Thanks in advance.

Lukasz Grabun

On Wed, 22 Sep 2004 21:02:01 +0200, Lukasz Grabun wrote:
> I have a prompt "boot:" but also all three
> lamps on my keyboard are lit and there's no responce to my hitting all
> keys... What is screwed up? Is it BIOS or my configuration the Slackware
> dislike? I am in despair. Help. :-)

Looks like a problem with ISOLinux to me (not a Slackware specific
problem). Try Google, there are probably a dozen other people on the net
that had the same problem, and solved it .

With kind regards,
Daniel de Kok

Lukasz Grabun wrote:

> Any tips and recommendations are deeply appreciated. Thanks in advance.

Maybe the installer thinks there's something fishy about your keyboard? I
suggest trying out a different keyboard for the installation.

Jeffrey

I had a similar problem with a USB keyboard.

On Wed, 22 Sep 2004 21:02:01 +0200, Lukasz Grabun wrote:

> Hi there,
>
> I googled a bit to find a solution to my problem. It seems, however,
> that no-one ever mentioned something alike. My current configuration is:
> AMD 2400+, 512 MB RAM, AsRock motherboard. Currently using Windows 2000.
> I've purchased Slackware 10.0 distribution today (I used to use 8.1 for
> quite a long time and really fancied it) as to install it on the
> remaining partition. But the installation process halts as soon as
> welcome screen is displayed. I have a prompt "boot:" but also all three
> lamps on my keyboard are lit and there's no responce to my hitting all
> keys... What is screwed up? Is it BIOS or my configuration the Slackware
> dislike? I am in despair. Help. :-)
>
> Any tips and recommendations are deeply appreciated. Thanks in advance.
>
> Lukasz Grabun

>> Any tips and recommendations are deeply appreciated. Thanks in advance.
>
> Maybe the installer thinks there's something fishy about your keyboard? I
> suggest trying out a different keyboard for the installation.

Yeah, that is the point. I have USB keyboard; the installation is
resumed after two minutes of inactivity. However, other problems
occured: the keyboard problem can also be solved by enabling USB legacy
option in BIOS. But the again, this causes some problems with hot plugin
and USB device detecting (the system hangs, IIRC).

This is a bit of concern for I have both USB keyboard and wireless mouse
and don't feel like switching to anything else just for the sake of
Slackware.

Back to the drawing board, nonetheless.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, Lukasz Grabun dared to utter,
> Yeah, that is the point. I have USB keyboard; the installation is
> resumed after two minutes of inactivity. However, other problems
> occured: the keyboard problem can also be solved by enabling USB legacy
> option in BIOS. But the again, this causes some problems with hot plugin
> and USB device detecting (the system hangs, IIRC).

I'm assuming by this that you've gotten Slackware 10.0 installed by now
and leaving the keyboard in legacy mode is causing problems not with
the installation, but with the base system. If that is the case, may I
ask what kernel you are using? If you are using bare.i please note that
usb support for your devices (indeed usb support period) is a module.
If this isn't loaded before hotplug, that might be your problem.

Optionally I recommend re-compiling a kernel that has support for your
devices built right in so they don't have to be laoded either by
rc.modules or hotplug to have access to them. This may solve your
problems.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFBU0yilKR45I6cfKARAtGDAJ9q8nz4c7qMkJZbKet8Ws wDD1AVpwCdEbUT
wPf0lYe6CMDgaRCm2FcaTSE=
=UIw3
-----END PGP SIGNATURE-----

Lukasz Grabun wrote:

> This is a bit of concern for I have both USB keyboard and wireless mouse
> and don't feel like switching to anything else just for the sake of
> Slackware.

I suspect that slackware will have no problem with your keyboard and mouse
after installtion. My suggestion was to make the necessary switch for the
installation only.

Jeffrey

pgp trash troll delete

Hicks, Alan
188 Shady Dale Dr
Lizella, GA 31052
478-935-8132

+Alan Hicks+ <alan@lizella.network> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> In alt.os.linux.slackware, Lukasz Grabun dared to utter,
>> Yeah, that is the point. I have USB keyboard; the installation is
>> resumed after two minutes of inactivity. However, other problems
>> occured: the keyboard problem can also be solved by enabling USB legacy
>> option in BIOS. But the again, this causes some problems with hot plugin
>> and USB device detecting (the system hangs, IIRC).
>
> I'm assuming by this that you've gotten Slackware 10.0 installed by now
> and leaving the keyboard in legacy mode is causing problems not with
> the installation, but with the base system. If that is the case, may I
> ask what kernel you are using? If you are using bare.i please note that
> usb support for your devices (indeed usb support period) is a module.
> If this isn't loaded before hotplug, that might be your problem.
>
> Optionally I recommend re-compiling a kernel that has support for your
> devices built right in so they don't have to be laoded either by
> rc.modules or hotplug to have access to them. This may solve your
> problems.
>
> - --
> It is better to hear the rebuke of the wise,
> Than for a man to hear the song of fools.
> Ecclesiastes 7:5
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
>
> iD8DBQFBU0yilKR45I6cfKARAtGDAJ9q8nz4c7qMkJZbKet8Ws wDD1AVpwCdEbUT
> wPf0lYe6CMDgaRCm2FcaTSE=
> =UIw3
> -----END PGP SIGNATURE-----

> I'm assuming by this that you've gotten Slackware 10.0 installed by now
> and leaving the keyboard in legacy mode is causing problems not with
> the installation, but with the base system. If that is the case, may I
> ask what kernel you are using? If you are using bare.i please note that
> usb support for your devices (indeed usb support period) is a module.
> If this isn't loaded before hotplug, that might be your problem.

I turned off hotplug feature. I don't care. Now the problem is that,
still, legacy mode disabled halts the lilo loader i.e. the timer is
counted down and if I was patient enough I would have Windows booted
after two minutes of idle waiting. Well, I am not. This all leads to
that I have legacy mode enabled. Now, the problem is, whether this is
not in conflict with my wireless mouse (also USB). Apparently, it does
not work under X.org (but this may be the problem with configuration
file for X, will check that later). The small device that "tracks" mouse
movements blinks its lights when I press button or move the mouse so it
does work. But the pointer won't move. Is it the legacy mode or the
congi file? (I think it could be latter; aw, I have included wireless
devices support in modules but it seems as a unproper choice - these are
only network devices - does it include mice?)

The kernel I use is the uncompiled standard one that is included in S.
distribution. I will compile it today or tomorrow (unless my mouse will
start to co-operate).


Further reports to come.

Lukasz Grabun

> file for X, will check that later). The small device that "tracks" mouse
> movements blinks its lights when I press button or move the mouse so it
> does work. But the pointer won't move. Is it the legacy mode or the
> congi file? (I think it could be latter; aw, I have included wireless
> devices support in modules but it seems as a unproper choice - these are
> only network devices - does it include mice?)

Yeah, answering my own to boost ego. Huh, excuse me.

Anyway, I guess it *is* not USB support, it is xorg and its
configuration file. I have IMPS/2 as protocol and /dev/mouse as device
location. It *should* work according to all documents and usenet posts I
was able to google. All necessary modules are installed (this includes
usbcore, ubsmouse, input, hid and mousedev). But the pointer won't move
though the receiver flashes its lights and except it won't move
everything looks just fine.

Any suggestions? (still, legacy mode is enabled to make keyboard work).

Lukasz Grabun