I-Appliance BBS
The Official Source for Internet Appliance Upgrades and Mods

Click Here!
BBS Main List | Sign In | Sign Up | Search | Help | Linux-Hacker.netReply to Thread | Printer |

Home / I-Opener Areas / I-Opener Technical Stuff
Hi, I'm trying to get the scroll mouse to work in Redhat 7 and get USB Ethernet to work in Redhat 7
Linux 7 tweaks? Anyone?

New MessageHi, I'm trying to get the scroll mouse to work in Redhat 7 and get USB Ethernet to work in Redhat 7 (modified 0 times) Johnson
Profile
Hi guys,
I didn't see the answer I needed so I'm appealing to you.
I searched the net and found a mouse scroll fix, but it's doing something weird. They said to change the XF86Config file to say:
Section "Pointer"
Protocol "IMPS/2"
Device "/dev/mouse"
Resolution 100
Buttons 5
ZAxisMapping 4 5
EndSection

and restart your X server.

Yet when I do this it makes my mouse bring up a menu when I move down and select (like left click) when I move the scroll up? Did I mis-configure this?

Also BoGos wrote a killer explaination of how he got Redhat 7 to work on the I-opener earlier, but in getting the USB-Ethernet to work he said to access /usr/src/linux-2.2.16, but I only see /usr/src/redhat...then further directories in redhat, but none of them being linux-2.2.16
Could someone write a very clear explaination of how I can get this D-Link 10/100 Usb-Ethernet device to work in Redhat 7 on the I-opener (which is now working fantastically ..thankyou BoGos)

Thanks again guys for your help!!

12-25-2000 03:43:28

New MessageRE:Hi, I'm trying to get get USB Ethernet to work in Redhat 7 (modified 0 times) Johnson
Profile
Someone Mp3boombox told me he didn't think that the I-opener could successfully be configured for USB in Linux..or that noone had as of yet...has ANYONE successfully gotten USB support working? ...stupid newbie question... do I have to recompile the kernal in the i-opener or do I have to pull the drive and do it from a cd rom in another computer? Please tell me I can do it from the I-op...PLEASE PLEASE!! he he
Thanks... oh crap am I desperate to get USB working...

Johnson

12-28-2000 17:29:32

New MessageRE:Scroll mouse on Redhat 7 and USB Ethernet to work in Redhat 7 (modified 0 times) sodmeister
Profile
Johnson -

I haven't played with scrolling mice on the
latest versions of RedHat. It used to be that
you needed "imwheel" running in order to get
scrolling to work. Look at the documentation
for imwheel under /usr/doc.

RedHat 7.0 changed the main compiler. The
kernel needs to be compiled with kgcc rather
than gcc. Also, the original distrubution had
incorrect header files for the kernel. You can get a lot of info at:

http://www.scyld.com

Checkout the USB stuff under Linux Network
Drivers.

To get around a lot of the kernel troubles,
I am using a distribution called KRUD. This
is RedHat, but with all the latest security
updates and extra goodies. KRUD is updated
monthly and costs about $7 with postage. It
is sold by:

http://www.tummy.com

The machine I'm using right now is a v4 with
a 3Gb HD and 128Mb ram. I've installed a
D-link DSB650 USB ethernet adaptor inside the
IO's case. I did need to add the DSB650 to
the recognized device table of the pegasus
driver. I then built the driver as follows:

cd /usr/src/linux From kernel src rpm
make xconfig Enable pegasus under
make dep USB section...
make modules

Eventually, you will get a new pegasus.o
module. Place this in /lib/modules/2.2.16-22
under the usb directory. There is a modules.dep file that you will add a line to
so modprobe, etc. know about the new module.

I've found the pegasus module to be a bit
clunky. It spews a lot of errors for when
it attempts to set RX modes. DHCP takes a
long time to init the DSB650 and come up. A
hard coded IP address is quick, however.

Hope this helps...


sod ( "The lunatics are on the grass..." )
12-29-2000 10:48:04

New MessageInstalling linux (modified 0 times) ASPguy
Profile | Email
Johnson,
How did you installed linux and what version of linux is that?

I've installed linux 12 times but only came to success using the Suse Linux. It has an auto monitor chooser so that there is a at least a basic display on the iopener.

Just wondered how you went in isntalling linux, which linux, and which display you had chosen so i can install linux myself on the iopener.

Thank you.

-ASPguy

12-29-2000 12:03:26

New MessageRedhat 7 not working... hope this helps (modified 0 times) Johnson
Profile
Hey,
Well this is what I did.. I first installed Windows, then installed partition magic and partitioned the drive with an area for lilo, swap, boot and root. I think took a Laptop hd to desktop computer converter and installed redhat 7 from that. (that is the trick to getting past the initializing memory freeze that was vexing us for so long). This will get you at least as far as being able to get a root login. If you try to startx at this time you will only be able to get to a blurred version of Xwindows. I got into this ####ty version of Xwindows and (earlier put in on my C drive in windows) pulled kens Xf86config file into the /etc/X11 directory (backing up my old one just for safety). Then I rebooted redhat 7, reran Xconfigurator. Now I copied what sodmeister wrote for me that really was the key.

"1. Place the I-opener specific XF86Config in /etc/X11, but
rename it to something else to prevent to overwrite. Once the
system is up, change it back to XF86Config.

2. It's taken me 2-3 attempts to configure the Cyberblade at
bootup. Use a Generic monitor with 60-90 Hz refresh and pick
the density option that has 800x600 at 60Hz (or was it 56Hz?)
and also shows a 640x480 option. It's about the 4th one in the
list shown. Also select 4Mb of memory, even though the Cyberblade
only uses 2Mb. Select 800x600 at 16 bits of color. Selecting more
bits of color seems to cause the "half screen" problem.

3. Avoid X altogether at bootup if possible. The default init
state should be 3 in /etc/inittab until you have X working OK.

4. Make certain that the X server installed is the SVGA server.
If your desktop machine is causing some other server to be installed,
then X will never work with the Cyberblade"

Now what actually got it working at the end was to make sure that your open file file of XF86Config file gets erased.. it was in the same directory as the one that I copied kens to, but it was called something like XF86Config~ (the tilde at the end). Once I erased that stupid thing and only kens xf86config file was left, I reran Xconfigurator with the above settins and Vwalla... it booted up as clear as Redhat 6.2 did.

Hope this helps.

Dont eat the yellow snow

12-30-2000 04:00:06

New MessageRE: X under Redhat 7 (modified 0 times) sodmeister
Profile
Johnson -

Glad to hear things are working for you with
X windows.

I suspect that kudzu is the culprit. It's
utility that tells you you have a new
hardware configuration. I'm thinking that it
places the Cyberblade in a video mode that
then messes up the configuration of X at
that point in time.

I just went ahead and told kudzu to ignore
the Cyberblade and brought the I-opener up
at runlevel 3. Logged in as root and then
ran Xconfigurator. I gave it the same values
as I tried to use under kudzu and the X was
configured properly the very first try!

This saves all of us one big PITA with Linux
on the I-opener. Now, if we can just get that
USB networking a little more reliable...


sod ( "The lunatics are on the grass..." )
12-30-2000 10:26:06

New MessageGreat...good to see you got it up... by the way (modified 0 times) Johnson
Profile
Just wanted to say..I confess I have never compiled a kernal and am as green as they come to linux. I've just been lucky enough not to completely screw something up. If anyone would give me a hand, or write a step by step on getting this frickin USB support... they will write songs in your name and I PROMISE to tell "legend" stories to my grand kids.. (when that day comes) about you....PROMISE!!

he he

Thanks,
Johnson

12-31-2000 03:15:20

New MessageBuilding USB modules for RedHat 7.0 (modified 0 times) sodmeister
Profile
Hey everyone, Johnson's a VIRGIN!

OK, to build a kernel and drivers you need
the source for the kernel and the compiler
to build it (kgcc).

I've been doing the "custom" install of
RedHat 7.0, this allows me to select such
things as code developement and kernel
hacking. I'm not certain what all packages
get installed when selecting these options,
but I do know that the following are vital:

kernel-headers-2.4.0-0.26
kernel-source-2.2.16-22
kgcc-1.1.2-40
make-3.79.1-5

There are probably other packages need as
well. I haven't "hand configured" kernel
building, just used the intallation option.

Any way, the source will be installed in
/usr/src/2.2.16-22. There is also a sybolic
link to this directory at /usr/src/linux. All
of your kernel building will be done in this
directory.

Once you are in /usr/src/linux, type:

make xconfig

This will bring up a window showing you all
of the various options for building the
kernel and drivers. The processor in the
I-opener is typically a 586 level processor,
so set that option. In the USB section, you
probably want to build the pegasus driver, so
select the 'm' option for pegasus to build a
module for it.

A word about modules. Linux can be built with
drivers installed into the kernel or the drivers can be built as modules which can be
selectively added to the kernel. The current
USB setup under RedHat 7.0 is run as modules.

Anyway, after you've done the configuration
and saved it, you need to type:

make dep

This step provides information on the setup
to all the various sections of the kernel
source tree. It makes certain that all of
the pieces are compiled in the same way, etc.

Now, you are set to compile something! For
the modules, type:

make modules

This will build all of the drivers, including
the pegasus module for USB, etc. It will take
a very long time on an I-opener since the
entire machine is rather slow.

If you want to make a new kernel, then type:

make bzImage

This will create a new kernel image down in
./arch/i386.

If all you want is to add some USB support,
then I would recommend against a new kernel.
The installation of a new kernel involves
put new load maps into /boot and installing
all of the modules for the new kernel in
/lib/modules. Your new kernel will most
likely come out as 2.2.16-23, so you will
need maps and modules for 2.2.16-23, but the
regular 2.2.16-22 kernel is fine as it stands.

OK, let's say you just want to make a nice
pegasus.o module and nothing more. After the
"make modules" command, you would have the
pegasus.o file in /usr/src/linux/drivers/usb.

Copy pegasus.o to /lib/modules/2.2.16-22/usb.
Then, cd to /lib/modules/2.2.16-22 and notice
there is a file "modules.dep". You will need
to edit this file and add an entry for the
new pegasus.o file. The entry looks like:

/lib/modules/2.2.16-22/usb/pegasus.o: /lib/modules/2.2.16-22/usb/usbcore.o

One line, a space or tab after the ':'.

Doing this allows the module utilites like
modprobe, etc. to know that pegasus.o needs
to have usbcore.o loaded in order to work.

The last thing is to make certain that the
pegasus driver is associatied with your
ethernet device. Add the following to the file /etc/modules.conf:

alias eth0 pegasus

The X windows network setup tool will only
allow you to select a network driver from
the /usr/modules/2.2.16-22/driver/net area.
The addition for pegasus in /etc/modules.conf
gets around this problem.

Anyway, by doing all of this, I was able to
add a line to the pegasus.c file so it would
recognize my D-Link DSB650 adaptor. A lot of
work for just one line, but it allows me to
network my I-opener and write long notes like
this one!

This is not as "step-by-step" as I would like
it, but I'll probably add more in time.

Hope this is helpful....


sod ( "The lunatics are on the grass..." )
12-31-2000 11:19:15

New Messagesodmeister What am I doing wrong? (modified 0 times) Johnson
Profile
Hi,
Well I JUST got back up..the drive I had been working on got dropped and died..well I reinstalled linux and later added on all the things you told me to... but when I got to the /usr/src/linux directory I typed 'make xconfig' and it seemed to go through some text...then just kinda error'd out? do you know what is the matter? Does it sound like something isn't where it should be. I'm typing the make xconfig when the Xf86config file I'm using is Kens... is there something missing? Dang I hope you get this..I'm stuck till you or someone else does?

Thanks,

Johnson

01-24-2001 22:47:30

New MessageRedHat 7.0 Kernel Building and "make xconfig" (modified 0 times) sodmeister
Profile
Well, there is some text as the make proceeds. Then, it puts up an X window with the
configuration options. You need to be runinng X, of course!

Sounds like your X still isn't working right. There is a text only approach, it's annoying
since it asks "Y/N/?" for EVERY option. Try:

make config

instead of make xconfig.

Since this whole thing of the Pegasus driver keeps coming up, I think we as a group need to
build modules for the appropriate kernel versions and have them available for download
somewhere. This would save the Linux "newbees" much trouble, although it's said that shared
suffering builds stronger relationships...


sod ( "The lunatics are on the grass..." )
01-25-2001 09:27:33

New MessageNo got that working..but still nothing? (modified 0 times) Johnson
Profile
Hi,
Well I figured out the X-windows thing after posting that... compiled the module (make xconfig)...make dep...make modules.., copied it to the correct area (pegasus.o file in /usr/src/linux/drivers/usb to /lib/modules/2.2.16-22/usb), made entry in modules.dep (/lib/modules/2.2.16-22/usb/pegasus.o: /lib/modules/2.2.16-22/usb/usbcore.o), added "alias eth0 pegasus" line to /etc/modules.conf:, but still nothing...in the post below he says "by doing all of this, I was able to add a line to the pegasus.c file so it would recognize my D-Link DSB650 adaptor. A lot of work for just one line, but it allows me to network my I-opener ..." Where is the pegasus.c file I think I might have deleted it on accident..maybe that's the problem... or is there something else that needs to be entered to tells redhat that we will be using this module in a network configuration? and what is the module called (was poking around in the network config and didn't see an obvious listing for the module.. saw something like eth0 16.. or someting..is that it..that was the closest I saw to eth0?
Thanks guys,
Jason
btw..will the same pegasus module that we compile here work in jailbait?
01-25-2001 11:30:28

New MessagePegasus USB under RedHat 7.0 (modified 0 times) sodmeister
Profile
/usr/src/linux/drivers/usb/pegasus.c

Should be the same directory where you got your pegasus.o module from.

Edit pegasus.c, adding an entry for the new D-Link adapter (clear case) into the
"usb_id_tbl" table. Notice that there is already an entry for the D-Link DSB-650TX,
we need to add an entry for the clear case DSB650 as follows:

{"D-Link DSB-650", {0x2001, 0xabc1, NULL},

This might not be the exact syntax, use the 650TX entry as an example. The new entry removes
the "TX" and change the first numbers to "0x2001, 0xabc1". I don't have a RedHat 7.0 system
here at work, so I'm doing all of this from memory.

What you've done so far sounds good. The pegasus.o module is in the proper directory, module
dependencies via modules.dep, etc. You will not see any usb modules listed in the network
configuration tool, it looks only at the modules in /lib/modules/2.2.16-22/net (not usb!).

It would help debug if you can post the USB messages from your /var/log/messages file. This
would give me an idea of how your USB is reacting to the ethernet adapter.

As for Jailbait, they use a different version of the kernel than RedHat 7.0. Someone has
already re-compiled the pegasus.o module for the D-Link DSB650 clear case. I've downloaded
it and applied it to the Jailbait build in my sandisk. Works just fine...


sod ( "The lunatics are on the grass..." )
01-25-2001 15:07:20

New MessagePegasus USB support under RedHat 7.0 (modified 0 times) sodmeister
Profile
Johnson -

Perhaps you don't have the other files setup for eth0?
Check /etc/sysconfig/network-scripts. You should see ifcfg-eth0 there.

If not, you can either use the network configuration tool to create this
file, or create it manually with the editor of your choice:

DEVICE=eth0
BOOTPROTO=static
IPADDR=192.10.10.1
NETMASK=255.255.255.0
ONBOOT=no

Obviously, you'd change the IPADDR and NETMASK to suit your network.

Don't give up hope! You're closer to being there than you might think.


sod ( "The lunatics are on the grass..." )
01-25-2001 15:17:59

New MessageWhat the hell? (modified 0 times) Johnson
Profile
Thanks for the help...I don't know if this is the magic bullet or not though.. My computer was running fine today, and now that I'm home I am trying to reboot into linux and it seems to be hanging where it says Checking Filesystems [OK] ??? Does this sound familiar... I know I'm a newbie but the last time this happened (the last time I was ALMOST there) I ended up pulling the drive and reformatting and installing linux...oh god please tell me that isn't the only fix? Thanks Johnson

OH BTW What is getting better speed increases without too much whining and fuss...the K6-2 or K6-3? Saw the big 557(or close to that)mHZ speed by mp3boombox... any suggestions

Johnson

01-25-2001 22:02:12

New MessageGREETINGS FROM MY I-OPENER'S LINUX BOX! (modified 0 times) Johnson
Profile
AHHH!! THANKS FOR THE HELP GUYS!! I FOUND WHAT WAS WRONG... I HAD SOME INVISIBLE FILES... PEGASUS.O~ AND MODULES.DEP~ FOR ALMOST EVERY ONE OF THEM... WHEN I DELETED THE FILES WITH THE TILDA AT THE END... IT CAME TO LIFE?
DO YOU KNOW WHY?
THANKS,
JOHNSON

OH BTW... WHEN I TYPE MOUNT /DEV/HDB IT ISN'T MOUNTING THE SECOND HD...I WOULD LIKE TO ACCESS JAILBAIT WITHOUT CRACKING OPEN MY I-OPENER AND UNPLUGGING? SECONDLY...DO YOU KNOW WHERE PEGASUS.O IS IN THE JAILBAIT TREE.. MAN IT FEELS GOOD TO BE RUNNING FINALLY..MONTHS AND MONTHS AND MONTHS AND NOW... THANKYOU!!! This is a great night for me! Thankyou!!

Johnson

01-26-2001 00:32:45

New MessageLinux and Jailbait, Oh My! (modified 0 times) sodmeister
Profile
Humm...

A file with a tilda on the end is usually created as a "backup file" when using an editor.
The "modules.dep~" happened when you edited that file, but a "pegasus.o~" sounds like you
opened pegasus.o with an editor. Editing binary files is generally not recommended.

As for the sandisk (/dev/hdb), it's correct that you can't mount it. Here are a couple of
reasons why:

1. /dev/hdb refers to the entire drive. You would only mount partitions for the drive,
so it's legal to mount /dev/hdb1 (for partition 1), /dev/hdb4 for partition 4, etc.

2. If you haven't copied over the Jailbait image onto /dev/hdb, then there aren't any
Linux filesystems on /dev/hdb1, etc. Therefore, Linux can't mount anything from hdb.

For Jailbait, the steps are:

1. Uncompress the Jailbait image. It's compressed to something like 14Mbytes. Use
the command "gunzip", "gunzip version6_fullinstall_img.gz". This gives you the
uncompressed file "version6_fullinstall_img".

2. Copy the image onto the sandisk. Use the "dd" command to do this.
" dd if=version6_fullinstall_img of=/dev/hdb ".

You're ready to boot up Jailbait, setting the BIOS boot option to boot from Drive D.
There is an updated version of the pegasus.o file for Jailbait. It lets you use the
D-Link DSB650 adapter.

I copied the new pegasus.o over to Jailbait by booting up Linux on drive C. Use the
command "fdisk /dev/hdb", then the "p" command to printout the partitions on the
sandisk. One of the partitions (forget which one) can be mounted to give you the
root filesystem from Jailbait. Mount this partition RW (so you can write it) and copy
over the new pegasus.o file into /lib/modules/2.xxxxxx/usb.

Jailbait isn't too bad! It requires you to login as root, then use the command "startx"
to bringup X windows. It has Netscape for a browser and several small pop3 mail clients
for getting Email. The sandisk is mounted read-only, so you can't save files to it, which
is the only noticable differents between Jailbait and Linux on a hard drive.

Have fun this weekend with Linux!


sod ( "The lunatics are on the grass..." )
01-26-2001 09:00:53

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