mdg

If you downloaded your iso's, did you check md5sums before burning to cd? It's possible you have a bad download

$ md5sum /dir/of/iso/file.iso

The md5 sums will be at the site you downloaded from

I recently moved to 10 OE and I'm having trouble with drive mounts. I can mount drives using eg

mount -t auto /dev/hdd /mnt/cdrom

but it mounts read only

I understand that supermount doesn't work in 10 - so how can I automount my fstab entries at boot?

I'm getting errors at boot with this issue, namely:

mount: mount: wrong fs type, bad option, bad superblock on /dev/hda1,
                     or too many mounted file systems
mount: mount: No medium found
mount: mount: /dev/fd0 is not a valid block device

Also, /proc doesn't load at boot

My fstab

/dev/hda1 /mnt/windows vfat iocharset=iso8859-1,codepage=850,defaults 0 0

/dev/hdb1 / ext3 defaults 1 1
/dev/hdb5 /home ext3 defaults 1 2
/dev/hdb6 /usr ext3 defaults 1 2
/dev/hdb7 swap swap defaults 0 0

/dev/hda6 /mnt/92home ext3 defaults 1 2
/dev/hda5 /mnt/92root ext3 defaults 1 2
/dev/hda7 /mnt/92usr ext3 defaults 1 2

none /proc proc defaults 0 0
none /dev/pts devpts mode=0620 0 0

/dev/hdd /mnt/cdrom auto umask=0,user,iocharset=iso8859-1,codepage=850,ro 0 0
/dev/fd0 /mnt/floppy auto umask=0,user,iocharset=iso8859-1,sync,codepage=850 0 0

[moved from Software by spinynorman]

What command did you use to compile the src.rpm?

If I had downloaded the file to /home/downloads, for instance, I would cd to that directory, then su to root and put

rpmbuild --rebuild NVIDIA_nforce-1.0-0261.src.rpm

Don't forget, case-sensitive

It seems from the error you gave that the name of the src rpm wasn't complete, unless you edited the error

If you're using the stock kernel with 9.2, you'll probably need to install the nvidia drivers. Click on the "Downloads" link at the top of the page and get the 0261 src.rpm.

You'll also need to get your kernel source. Type "uname -r" (no quotes) to see what kernel you are running and download the matching kernel source from http://www.kernel.org

Install the kernel source rpm first, then compile and install the nvidia src.rpm using

"rpmbuild --rebuild name-of-file.src.rpm" as root. That will build a rpm for you and put it in /usr/src/somewhere (I forget where exactly,I'm not on Linux right now). Near the end of the compilation there'll be a line telling you where the file went. Install the rpm

If all goes well, run Drakconnect, select the nvnet driver and you should have a working LAN

There's another thread on this here, which might give more details

7/10

I missed bogomips(?), the apache question and the window manager question (stupid, wasn't thinking)

I'm using a Microsoft Explorer, it's also a bus mouse on a PS/2 connection, like yours, only I'm still in 9.2

My XF86Config-4 entry has /dev/psaux, not /dev/mouse, maybe changing your entry around might make a difference

Having said that, I think Mdk 10 uses a different way of listing devices than 9.2 (something to do with udev?), so maybe it's meant to be /dev/mouse

Anyway, no harm trying, you can change back if it doesn't work

Right click on the taskbar then click Add - Applet - Pager

As for the bios message, I found an explanation at this address:

Why does the BIOS string say PII and not PIII ?

This is the BIOS Base Support Message and is meant to say PII (It means that the BIOS will support the PII as well as PIII.

You should see the following line recognizes the PIII correctly

(See BIOS message)

Also, have a look at this site, there are a few questions and answers about your board. The first question is in Dutch, but it relates to adding a 80GB disk to this board and the disk not being recognized. Seems like the solution to all the problems is a bios upgrade

Of course, there's still the possibility that the CPU is dead...

Windows 3.1 up to XP

Linux distros I tried for varying lengths of time before going back to Mdk:

Lycoris

Redhat

Suse

Gentoo

Arch

Debian

Libranet

I built a new system a month ago and my research for that showed the importance of the power supply. The manufacturer is more important than the wattage. A good 300W will beat a mediocre 400W in quality of power and stability for your system.

Get a name brand (Antec, Enermax, Thermaltake etc). The Enermax 365 and 465 both have great reviews

Krusader is a two pane graphical file manager modelled on the ex windows commander. This is the forum, there's a download link there

I had similar problems with Mdk 9.2 and 2.6.2 kernel. Details in this thread.

Are you sure you have the right kernel sources installed? My problems disappeared when I used the 2.4 kernel with matching sources.

I deleted the file and rebooted - no "bringing up eth1" anymore. Thanks aru

aru, as requested:

[root:marc]# for file in  /etc/sysconfig/network-scripts/ifcfg-eth*; do echo $file; cat $file; done
/etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=dhcp
IPADDR=192.168.2.101
NETMASK=255.255.255.0
NETWORK=192.168.2.0
BROADCAST=192.168.2.255
ONBOOT=yes
MII_NOT_SUPPORTED=yes
NEEDHOSTNAME=yes
/etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE=eth1
BOOTPROTO=dhcp
NETMASK=255.255.255.0
ONBOOT=yes
MII_NOT_SUPPORTED=yes
NEEDHOSTNAME=yes

I didn't find the relevant part in dmesg, but it was in the boot.log:

Mar  2 12:58:13 mguise network: Setting network parameters:  succeeded
Mar  2 12:58:13 hostname network: Bringing up loopback interface:  succeeded
Mar  2 12:58:17 hostname network: Bringing up interface eth0:  succeeded
Mar  2 12:58:17 hostname network: Bringing up interface eth1:  succeeded
Mar  2 12:58:17 hostname internet: Checking internet connections to start at boot succeeded
Mar  2 12:58:18 hostname portmap: portmap startup succeeded
Mar  2 12:58:20 hostname ntpd: ntpd startup succeeded

I have a small home network set up as follows:

Cable modem connected to Edimax router via WAN port

Mdk 9.2 box connected to router (LAN port)

XP box connected to router (LAN port)

All IP's are handled by DHCP

Internet sharing works and file sharing works from Mdk only - I can browse XP dirs from Mdk box, but can't get into Mdk from XP (but that's not the issue right now)

When I bootup Mdk, it loads both eth0 and eth1. I only have one NIC on either machine, so what is eth1?

Here's the result of ifconfig

[root:marc]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:04:61:53:EC:B6  
         inet addr:192.168.2.101  Bcast:192.168.2.255  Mask:255.255.255.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:74166 errors:0 dropped:0 overruns:0 frame:0
         TX packets:77247 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:100 
         RX bytes:92538833 (88.2 Mb)  TX bytes:7197295 (6.8 Mb)
         Interrupt:11 Base address:0x1000 

lo        Link encap:Local Loopback  
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:306 errors:0 dropped:0 overruns:0 frame:0
         TX packets:306 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0 
         RX bytes:20474 (19.9 Kb)  TX bytes:20474 (19.9 Kb)

And ifconfig eth1

[root:marc]# ifconfig eth1
eth1: error fetching interface information: Device not found

Bootup also takes a long time to bring up eth0 (eth1 is picked up immediately after)

Is eth1 maybe the router?

Check in /etc/X11/XF86Config-4 if you have the "z-axis" line in the Input Device section. It should look like this:

Section "InputDevice"
   Identifier "Mouse1"
   Driver "mouse"
   Option "Protocol" "IMPS/2"
   Option "Device" "/dev/psaux"
   Option "ZAxisMapping" "4 5"
EndSection

I don't know how your mouse is set up, so don't copy the other lines unless you think they fit your config

Don't know how to do it myself, but this link might help

Thanks for the input, I think I'll leave it set up the way it was. The router has a firewall built in, so it should be reasonably secure

My home network setup right now is like this:

Setup 1:

Cable modem connected to router (WAN port)

LAN port 1(router) goes to Mdk box

LAN port 2 goes to XP box

Both machines can connect to internet, but I haven't figured out file sharing yet (that's for another post)

I'm wondering if it's not better to setup like this:

Setup 2:

Cable modem connects to Mdk box (eth0)

Mdk (eth1) goes to router (WAN port)

LAN port 1 (router) goes to XP box

My main objectives are internet sharing and file sharing

Any advantages of one method over the other?

1) 2.6 has a fully working nvidia lan driver

The nforce driver included in the 2.6 kernel is forcedeth, which would not work with my mboard. The driver in the nvidia src.rpm is nvnet, which did work. From reading other forums, I've seen that the forcedeth driver works only in a few cases. The majority of people using the nforce2 LAN are using the nvnet drivers

Raystorm, make sure you back up everything, like fissy suggested, you'll be using a lot of cooker packages to solve dependencies

I'll agree with arthurking - don't bother with 2.6 right now. Get it working with the 2.4 kernel and you can move up later.

I had the 2.6.2 kernel running when I tried to install nvidia's src.rpm and after three days of trying, I eventually broke my system by updating with cooker to install needed file versions and solving deps.

I reinstalled with 2.4.22 and after minimal effort got sound and LAN running with nforce drivers.

I'm also in no hurry to install the 2.6 kernel again

I installed glibc-devel-2.3.3-10mdk plus other dependencies.

If I look at bvc's output of urpmf irq.h, I can find all those files in the right places on my box, but if I do "urpmf irq.h" (or any other disputed file), I get no output.

Are these files somehow not in the path?

My whole point here is to get the onboard LAN to work, but it seems a lot simpler to me to just install a NIC and be done with it

I have glibc-devel-2.3.2-14mdk installed and 2.6.2-1mdk kernel running with kernel-source-2.6.2-1mdk installed

[root:marc]# rpm -q glibc-devel
glibc-devel-2.3.2-14mdk

[root:marc]# uname -r
2.6.2-1mdk

[root:marc]# rpm -qa | grep kernel
kernel-2.4.22.6mdk-1-1mdk
kernel-doc-2.4.22-5mdk
kernel-2.6.0.1mdk-1-1mdk
kernel-2.6.2.1mdk-1-1mdk
kernel-source-2.6.2-1mdk

nforce.src.rpm still won't work

If you're using KDE, go to Control Centre-peripherals-mouse select the Avanced tab and adjust the bottom option, "mouse wheel scrolls by..."