Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 151687

Summary: loadkmap fails to load keymap during boot of LiveCD
Product: Gentoo Release Media Reporter: Xake <kanelxake>
Component: LiveCD/DVD/USBAssignee: Gentoo Release Team <releng>
Status: VERIFIED WORKSFORME    
Severity: minor    
Priority: High    
Version: 2006.1   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Xake 2006-10-17 03:17:12 UTC
At least the lastest two (including 2006.1) LiveCD have not loaded the keymap you specify during boot. Choosing se/32 gives me:

>> Loading the ''32'' keymap
loadkmap: /dev/vc/0: No such file or directory

loadkeys sv-latin1 after bootup works.
Comment 1 Xake 2007-01-13 13:18:30 UTC
Today I used the 2006.1-minimal installation CD and with this I could change keymap without problems so apparently this problem is limited to the LiveCD.
Comment 2 Andrew Gaffney (RETIRED) gentoo-dev 2007-01-13 17:51:37 UTC
I just tried loading the same keymap on the x86 2006.1 LiveCD and it worked without a problem.
Comment 3 Xake 2007-01-14 09:14:51 UTC
I think I had a bad burn. New LiveCD works.

Maybe implement a function like Ubuntu for testing the CD-integrity?
Comment 4 Chris Gianelloni (RETIRED) gentoo-dev 2007-01-15 17:31:47 UTC
Well, we do already ship the DIGESTS file, which can be used to verify the integrity.
Comment 5 Xake 2007-01-15 17:50:15 UTC
Well I downloaded it with bittorrent and it is self-checking, is it not?
But I think I tested it against the digest since I was unsure about if my client did at the time.
So either it was a bad burn (and I think it is this one since it was like that from the very beginning) or something got scratched, something that is imopossible to check with just that digest (and I think that is why Ubuntu have their "integrity-check".
Comment 6 Chris Gianelloni (RETIRED) gentoo-dev 2007-01-15 18:13:45 UTC
(In reply to comment #5)
> So either it was a bad burn (and I think it is this one since it was like that
> from the very beginning) or something got scratched, something that is
> imopossible to check with just that digest (and I think that is why Ubuntu have
> their "integrity-check".

Uhh... you can check it.  All Ubuntu/Red Hat do is verify the CD against a checksum.  You can run md5sum/sha1sum against a mounted CD.

cat livecd-i686-installer-2006.1.iso.DIGESTS
md5sum /mnt/cdrom

=]

Anyway, this isn't a discussion place, so I'll quit spamming everyone with these emails.