[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#65431: Thinkpad 365x problem fixed



I found a solution to my problem loading keymaps (though
not until after I compiled my own version of the 
boot-floppies ;) ). The boot-floppies worked fine if
I used the dd command:
	dd if=resc1440.bin of=/dev/fd0 bs=1k
but not if I did:
	dd if=resc1440.bin of=/dev/fd0
(which defaults to bs=512b).

I duplicated the behavior of failing at at the loading
keymap section for multiple potato boot images and
multiple floppies.  

Trying the same thing with the slink boot images I found
that booting would fail much earlier - while the loading
root.bin message is on the screen (while the rescue floppy
is in the drive, but after the initial "press enter" to boot
message).

Both 512 and 1024 b bs images work fine with my desktop
machine.

I don't understand why using bs=1k works, when the documentation
makes it seem like you should use bs=512. I don't know if this
is a result of the notoriously flaky Thinkpad floppy controllers
in general, or if it is a fault of my machine in particular. So
I anyone with a Thinkpad (365X in particular), could see if they 
duplicate this behavior I would appreciate it.  Unless it is
duplicated, this bug can probably be safely closed.

Thanks.

-- 
Jim Crumley                 |
crumley@belka.space.umn.edu |
Work: 612 624-6804 or -0378 |

> Subject: Keymap not loading on Thinkpad 365x

> Package: boot-floppies
> Version: 2.2.15-2000-06-07
> Severity: Normal

> When trying to install potato on an IBM Thinkpad 365X, I can
> not get the keymap to load.  Everything loads normally until
> the point where I choose a keyboard. I choose keyboard type qwerty/us
> (and I get the same problem with other types), and I get the
> error message "Error loading the keymap i386/qwerty/us.bmap
> from /etc/keymaps.tgz."

> Also, fdisk isn't happy with my hard drive, but I can't partition
> with fdisk because the shell won't take input, probably because
> of the keyboard problem.

> I've had this same problem with boot floppies set 2000-05-05.  The
> same set works fine on my desktop machine.




Reply to: