I-Appliance BBS
The Official Source for Internet Appliance Upgrades and Mods
Amazon Honor System Click Here to Pay Learn More
BBS Main List | Sign In | Sign Up | Search | Help | Linux-Hacker.netReply to Thread | Printer |

Home / I-Opener Areas / I-Opener Technical Stuff
Configuring Linux
How to set up the various Linux configuration

New MessageConfiguring Linux (modified 0 times) CodeDemon
Profile | Email
I know that almost everyone has done it...

I've looked and searched, but there is no thread on installing individual
OS's on the iOpener. I've been hanging out here for a couple of months now, and
while there are discussions on bits & pieces, there is no set path in doing this.

I admit I'm a newbie to Linux, specifically Mandrake, I've gone and did all
the basics to get started with the least engineering effort.

My setup is:
IO V4, BadFlash BIOS, Drive Adapter, 4.8G HD, 128M SODIMM, Cooling Fan, USB HUB/NIC.

So you can see I'm ready to roll here, but I can't get over the hump. I'm sure that its probably just one little change, but I can't see where it needs to be. I've put Mandrake Linux on the HD (IBM Travelstar 4.8g) and moved it over IO.

But now I get a vfs Kernal Panic message. It says to change the boot= option I'm guessing that this is because
the original host machine hardware was so different from the IO.

I know that lilo.conf needs to be modified, and I'm guessing other files do too, would anyone care to share thier expertise in this?

Any help would be greatly appreciated.

02-13-2002 21:03:18

New MessageRE:Configuring Linux (modified 0 times) c0nsumer
Profile | Email
I've got the same thing here, except I was moving a Slackware install over. Not sure what's wrong, but when I figure it out I'll be sure to post it here. If anyone else has any suggestions, please feel free to chime in.

-Steve

02-19-2002 19:07:20

New MessageRE:Configuring Linux (modified 0 times) Linuxguru
Profile | Email
If you're installing slackware, you will find the going easier if you do the following:

1. On the host (non-IO) system, create a bootable DOS partition large enough to hold the contents of the entire \slakware directory tree from the install CD (say ~1 GByte, maybe less). Leave about a GB or more for the actual Linux root filesystem.

2. Install DOS on this partition and make it bootable.

3. Verify that the drive is bootable to DOS on the I-Opener.

4. Re-install the drive on the host, and copy over the entire contents of the \slakware tree.

5. Create a directory called \linux, and copy

(i) a kernel image from \kernels\..., say bare.i\vmlinuz.
(ii) an installer ramdisk image, say rootdsks\color.gz or text.gz.
(iii) loadlin.exe from \kernels.

6. Create a batch file called install.bat, with the following two lines:

smartdrv /c
loadlin vmlinuz root=/dev/ram rw initrd=color.gz

7. Transfer the drive to the I-Opener, boot into DOS and do the following:

cd linux
install

8. Once it boots to the Linux install root prompt, proceed to install slackware as per the instructions in the booklet. Choose "Install from hard drive partition" in Setup. Don't install LILO and don't create a boot diskette during the installation (you can install LILO later).

9. You can continue to boot Linux from DOS using loadlin. Create a batch file called linux.bat in the \linux directory, with the following two lines:

smartdrv /c
loadlin vmlinuz root=/dev/hda2 ro initrd=

(substitute the actual name of your root partition in the root= argument).

10. Later, you can try installing LILO and then get rid of your DOS boot partition entirely.

02-19-2002 20:23:55

New MessageRE:Configuring Linux (modified 0 times) scaife
Profile
I had this problem at one time... I believe I fixed it by typing "linux ide=noprobe" at the LILO boot prompt... not sure though
02-19-2002 21:06:49

New MessageRE:Configuring Linux (modified 0 times) Ragnar1
Profile
linuxguru,
Your method of installing linux look like an easy way to get the most out of the k6+s without yet knowing too much about linux. Boot to the dos partition with k6clk.exe on that partition and using the appropiate line in the autoexec.bat file. Then loadlin xx, in my case Mandrake 8.1. Mandrake 8.1 definitely needs the higher speed, plus 256mb memory module. It taxes the iopener hardware considerably. Probably as much as XP. Might have to try it when I can find the time. 8-)
02-19-2002 22:45:10

New MessageRE:Configuring Linux (modified 0 times) scaife
Profile
It might have been "linux hdb=none", too... Try it and let me know if one of them works!
02-20-2002 08:52:16

New Messagehdb=none (modified 0 times) c0nsumer
Profile | Email
Scaife,

Appending 'hdb=none' took care of it. Thanks very much. It was getting late last night and I was banging my head against the wall. Guess I needed more patience to try other things, including a slap upside the head. hehe. I guess the Sandisk was somehow pissing the kernel off. If I get the Sandisk working under linux (haven't checked if there are any posts on doing it or not) I'll post how. Right now it's not very high on my list of priorities. Getting that MP3 player for the kitchen is, though. heh.

-Steve

02-20-2002 16:09:17

New MessageRE:Configuring Linux (modified 0 times) scaife
Profile
No problem, Steve. I don't understand why the Linux kernel has problems with the Sandisk, but oh well... :) Good luck!
02-20-2002 21:19:59

Reply to Thread | Printer |
All times are PSTPowered by UltraBoard v1.62



Copyright © 2000, Netmake Inc. All Rights Reserved.
See Terms and Conditions for more information.




i-opener opener laptop notebook computer help drivers dll free windows dos repair fix linux mac macintosh 2000 95 98 nt pc configure hardware software sound video netscape explorer network networking lan wan software cmos fat bios printer card mouse modem ide scsi cd rom controllers scanner tape hard drive cgi scripts source code mp3