libretto install

Forum: Laptops
Topic: libretto install
started by: southpaw cowboy

Posted by southpaw cowboy on May 18 2005,21:59

I am a linux newbie,someone please help with this install so I can teach myself linux and not have to ask stupid questions! I have installed fedora onto my desktop (no probs,loads of info) I wanted to carry a linux machine everywhere and my
reduntant (cos win95 is awful) libretto seemed the best bet. so naively i have for my second ever install gone for dsl on the libretto 50 ct. I have got dsl installed on the hd, I went for the inelegant but simple solution of fitting the hd into my desktop. the problemm occurs when I try to run it up back in the libretto. all seems to go well until it gives me the kernal panic message and a hex code, as follows:

code: 39 46 04 74 0e 31 c9 ba 03 00 00 00 89 f0 e8 6c aa fe ff 5b
<0>kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
I havent a clue, i,m searching all over for error cdes but havent found any yet. thanks in advance to anyone with some good gen!

Posted by Guest on May 22 2005,03:37

When you said "all seem to go well", what exactly were you doing? What you just saw is a core dump, and it can be caused by a lot of things.

Posted by cbagger01 on May 22 2005,16:55

Try searching google for:

libretto linux

or

libretto knoppix

for help.

Also, there are a couple of guys here that use DSL on a libretto. They drop in every now and then. So help may arrive at some point.

Posted by skaos on May 23 2005,11:34

Also take a look at < http://www.linux-on-laptops.com/ >

Posted by southpaw cowboy on May 23 2005,21:51

when I say all was was going well, I put the HD back in the laptop and booted, LILO started ok and it gets as far as the color messages but once past this the messages scroll V fast and the screen reads:

Code: 39 43 04 74 11 b9 01 00 00 00 ba 03 00 00 00 89 d8 e8 c9 ab
warning ... fsck .ext2 for device /dev/hda1 exitied with signal 11
<1>unable to handel kernel paging request at virtual address 236892b4
printing eip
c012dce5
*pde = 00000000
oops: 0000
cpu: 0
EIP: 0010:[<c012dce5>] not tainted
EFLAGS: 00010086
eax: 236892b4 ebx:c0036150 ecx:00000020 edx: 00000020
esi: 236892b0 edi: c02a42bc ebp: 00000001 esp: cod4fed4
ds: 0018 es: 0018 ss:0018
process checkroot .sh (pid: 24, stackpage=cod4f000)
stack: (loads of stack codes at this point)
call traced: (loads of codes agaIN)

and finally the code I i've put in my first post.

I wouldn't usually ask for a helping hand but I am totally new to linux at command line level and although I am learning a bit on my desk top I really need to be able to have linux in my pocket to be able to spend some serious time on it. Thanks for all the suggestions so far. SPC

Posted by Guest on May 24 2005,17:21

Can you try booting up that libretto again and tell us that last colored message you see, just before the core dump? Lilo boots, but probably something went wrong during the transfer of control.

Posted by southpaw cowboy on May 25 2005,11:48

Running kernel 2.4.26 (in yellow)
Running from HD checking file systems... (in blue)

Posted by Guest on May 25 2005,17:18

I have seen this a few times before, and all of them was caused by different things. So you will have to try doing some elimination to narrow-down the cause of the problem.

First, I think you have not yet run the DSL on the libretto prior to this attempted hd-install so I will recommend for you to do so using the "Loadlin install" procedure. Details are available from the DSL Documentation pages.

Format that libretto hd to FAT32 using a Windows Emergency Boot disk, making the hd bootable if you can. Then copy the folders "Knoppix" and "isolinux" (inside the folder "boot") from the CD onto the libretto hd. You may need to use that other desktop that you used before for this. Obtain loadlin.exe and put it inside the "isolinux" folder. Create that "options.txt" file inside the "isolinux" folder. Then follow the instructions in the "Loadlin install" procedure for starting up DSL. If this went well, then your problem was caused by errors during the hd-install.