scoonma

Haven't tried that with a windows entry in lilo, but you can always access linux by just typing "linx". Maybe it works with other entries, too? Otherwise I'd also suggest to use GRUB.

Cheers,

scoonma

There's nothing wrong; you've made it! You have libinst installed now in /usr/local.

Libraries have been installed in:

/usr/local/lib

The messages at the end are just the rest of output from "make". It claimed to have nothing to do because it succeded above. :-)

I'd add one ore two of the nameservers listed here to /etc/resolv.conf:

http://www.dslreports.com/faq/7525

Maybe you can find additional help here:

http://www.dslreports.com/forum/sympat

Good luck,

scoonma

Please check DNS and firewall settings

(see: https://mandrivausers.org/index.php?showtopic=34218 )

Cheers,

scoonma

Uups, should have inspected the numbers more closely! :blush:

I didn't want to argue against HAL - just meant to disable it temporarily for testing purpose. If anything goes wrong, you'd best be off with a most simple config, and add components subsequently. (KISS in error searching ;-)

Cheers,

scoonma

Hi Lone,

when it says: "Connected", this is actually the case! You don't need to change anything. If you click on the icon, you're obviously disconnecting! :-)

Greetings,

scoonma

Okay Peter let's try to sort this out. You wrote:

On the Connections icon (in the bottom right-hand corner of the screen, it looks like two lumps of shishkebob on a stick at a 45 degree angle) if I hover the mouse over it it says "Network is up on interface eth0". If I pull the cable it says "Network is down...".

This is absolutely normal, and meant to be this way.

> ifconfig eth0

Link encap: Ethernet

HWaddr 00:02:55:8A:69:1D

inet addr: 192.168.2.13

Bcast: 192.168.2.255

Mask 255.255.255.0

inet6 addr: fe8...

Scope:link

RX packets: 343 errors: 0

TX packets: 2332 errors: 0

RX bytes: 37KiB

TX bytes: 167 KiB

Interrupt: 20

 

netstat -r

Dest 192.168.2.0

default 192.168.2.1

Looks good, too! Your machine has 192.168.2.13 as IP address.

Default route is 192.168.2.1. This means your network routing defaults to that address, which is most probably your DSL Modem. So your machine is connected to it and all well! You'll presumably just have to find out about two important issues:

a) DNS service

b) firewall issues

a) Is your provider giving your a DNS server number automatically? If yes, you likely can choose 192.168.2.1 as DNS address on your machine, or obtain it from your modem using dhcp. If no, you should find out which DNS servers your provider is giving you, and use that one. You probably can "ping 192.168.2.1" in the scheme you've given above. If not, temporarily remove your firewall. Can you ping it now? If yes, try to ping the DNS server you are using. (You can end ping by pressing Ctrl-C).

b) This is more often a mess than actually doing sth right with home users. Firewalls were never meant to work on the same machine containing user data, but in the middle between "the big wide world" and local networks. I know there's "personal firewalls", but if you don't really know the concept, you can probably stay without one. Correct firewalling is a science on it's own, as you have to understand networking in detail.

If your modem provides a hardware firewall, I'd suggest to use that one and leave your local machine without. If you do not want to do this, you should delete previous functionality and set it up anew AFTER your connection is working. (On firewalls and security see also http://www.iks-jena.de/mitarb/lutz/usenet/Firewall.en.html )

If you're using shorewall, install iptables-ipv6 also and *deactivate* IPv6 (you actually don't need it, right?) within shorewall.conf (resides in /etc/shorewall). Small editors of your choice are "joe" or "nano"; vi can really be a pain in the ass, especially if you're new. I'd suggest to "urpmi nano" from console window and apply changes. (Shorewall authors advise to disable IPv6, see config file.)

I don't know what XP is doing to your modem, just know about Mandriva. :-)

The method above *should* work. I know these problems well because of my own experiences...

Good luck,

scoonma

Ian is right: The symbolic links are all well, if they point to a single device, but you'd possibly run into probs if cdrom and cdrom0 pointed to different devices, if there was only one dev reading CDs. I thought this would maybe the case.

Do you still have the "pamconsole" and "managed" options enabled with /dev/hdc? I've never used them.

You probably have a little mess now, right? So I'd suggest to remove the cdrom entry from fstab and get it automatically detected on next reboot by harddrake service or from MCC.

Hal is good for comfortable userspace access to the cdrom, but it's not a "core linux" app. After having a installed your cdrom entry anew, I'd disable HAL, try to insert a CD and manually mount is as root. ("mount /mnt/cdrom") Does this work? If not, what is the output?

HTH,

scoonma

Hi Gul,

your first entry for a nameserver is not valid (must be in range 1-254). Make sure you choose a valid DNS server here.

(For more info on networking, see http://www.idevelopment.info/data/Networki...ng_Scheme.shtml

for example).

Greetings,

scoonma

Hi Chris,

did you *both* change /etc/fstab and grub entries, as Ian recommended?

Normally the booting partition is of type "primary" and internall, thus residing on /dev/hda1 or /dev/sda1 or similar. Did you choose /dev/sda as boot device within grub?

The error message you posted suggests that you should specify a different mount option, maybe also a different filesystem type. Which fs type is /dev/sda1 now?

Regards,

scoonma

Okay, here's some more concrete stuff:

1) Probably not related to other distributions, I found strange dependancies within the init scripts/services: Keytable is relying on netfs which is relying on portmap. Surely there are situations where this is essential (network boot,...), but for a "normal" desktop system? I don't need networking filesystems, and don't want to have a server answering RPC calls. So this is over-complex. I'd rather have a small, fast-booting system!

2) Colored data! This very fine principle is already implemented in "ls" (LS_COLORS). Why not integrate it in nautilus? Gnome-Commander is already able work in this way.

3) Many of us will have real 3D accelerated desktops in the future. By now, 3D stuff was mostly for gaming 'n stuff. But what can be done using this feature not only for wobbling windows? Think about a colored 3D representation of your machine, kernel in the middle, ROM and hardware stuff on a level below, RAM on a level above. Hard drive data could be grouped around the kernel in a circle, segmented to drivers, libraries, scripts, sourcecode, binaries,...

Lust for a flight inside?

Let's put the fun back into computing! ;-)

Definitely confirmed: SLAX is great, and the module concept is simply marvellous and double precious using USB flash drives/memory sticks: Just throw the *.mo files you need in the /modules dir and the soft is ready after next boot. Maybe this is the future of installing apps 'n stuff? Plus, you can use software modules off the web (using livemod). How cool is this?

I've made a working device by this method:

1) Load the slax popcorn edition iso to harddisk.

2) Loop-mount the image to get access to the file structure.

3) Copy all content to a tmp dir for working purpose.

4) Throw in all desired modules.

5) Create a filesystem and format with reiserfs (why stick to DOS16?)

6) Copy content from tmp dir to usb-stick

7) Use lilo to install a bootloader into it's MBR.

I could have stuck to the "normal" SLAX method, but wanted to be able to access a system by standard means. As in most cases this resides on /dev/hda1, I've integrated the option in lilo. Surely this still can be improved.

(Ever wanted to show your friends what xgl/compiz can do to their bloated gaming hardware? Okay, you'll need additional stuff, but the very module is less than 15 MB ;-)

More details on request, additional info can be found here:

http://www.slax.org/forum/viewtopic.php?t=7094

Greetings,

scoonma

P.S. As Mandriva derives from RedHat which derives from Slackware, I wonder about few... :-)

Why not use the easy to configure rp-pppoe package? It even has a gui...

I don't know if it's working with pppoa connections, as I naver had one of them, though.

John is absolutely right: It's *not* appropriate to use any pppoe software here (as their purpose is building an ethernet connection over a ppp line all using *software*).

Peter mentioned it in his first posting: He uses a Speedstream (DSL) modem to establish the ppp connection, so that connection to the net is made by hardware. On the other (local) side is ethernet. So the LAN option for configuring is correct. You'll probably succed if you configure eth0 for dhcp use. And you can go on using lisa ;-)

A gstreamer-alsa dependancy would be the only strange aspect here, as gstreamer and alsa are packages related to sound (output).

Good luck,

scoonma

the network icon in te system tray now indicates that all the interfaces are down, inspite of the fact that my modem is connected to the server. wat could be the problem with that now? how to connect the interface to the modem, manually?

I'd suggest to delete network icon from the panel, possibly update the related applet ("urpmi --update gnome-netstatus" as root) and reinstall the applet manually within the panel (easy: right-click panel & add icon).

You should be sure you have a working gnome environment (could check with "urpmi task-gnome-minimal")

Ups - just saw you're probably using kde. But the idea is all the same. Just find out which applet/package kde is using for this purpose.

also, what are dhcp? can those pose any restrictions?

Dhcp is a protocol used by your client (your local machine) to determine it's internet address (often shortly referred to as "IP") dynamically. Normally bigger companies or organizations have static IPs, the rest of the world uses dynamic ones. Thus by an address the DHCP server on the other side is giving you, you are able to connect to the "outer world". :-)

HTH,

scoonma

The driver has probably changed your xorg.conf file (residing in /etc/X11). You could go to this dir and check for older (working) versions of xorg.conf for your keyboard layout. If there are any, simply copy over the new one, or adjust the InputDevice Section for your keyboard accordingly.

HTH,

scoonma

Yeah, the filesystem is an important point. It should be really stable for data. I don't care much about an fs being exploited for "desktop use" or database search function stuff. This is not what is was made for, and resembles of the annoying idea to use internet domain names for marketing purpose.

I only once stumbled over a really "rock-hard" filesystem, that would allow the following: Turn computer main power off immediately or crash during a writing process, but nearly no data loss(!), filesystem integrity preserved.

This thingy is SmartFilesSystem (SFS) for AmigaOS. But as it resides within GPL type world, porting should be possible somehow. At least there are some interesting ideas in it.

More info:

http://strohmayer.org/sfs/

http://sourceforge.net/projects/smartfilesystem/

Greetings,

scoonma

Hm. The entries look good - at first. :-)

Besides of an error elsewhere, I could only think of the following:

a) There's a comma instead of a period within some entry (which may not stand out in the pic you sent, and can also be hard to detect even in the interface).

b) There's a trailing space character following one of the last digits.

Can you leave out the second DNS entry but use the third one (should work, too)?

(You should also use a "real" hostname.)

HTH,

scoonma

Hi ro,

you wrote:

Well trust me i am entering the correct 1.2.3.4 format value...

Well... no ;-)

Could you please post the *exact* string you entered here?

Regards,

scoonma

Once having cdrom problems I discovered quite a "multitude" of cdrom entries in /dev. In particular, there was a directory called cdroms with different entries plus the "normal" devs and symbolic links. I had to clean things up before being able to go on normally.

Maybe this was due to an update, or because KDE / GNOME or different apps handle cdroms differently?!? (Can't check this anymore now.) Did you ever use autofs/supermount in conjunction?

If you should find a similar situation, please post all relevant entries in /dev here (before possibly damaging your system).

HTH,

scoonma

Hi shemz,

this sounds like a DNS problem to me. Please check the file /etc/resolv.conf for a valid nameserver entry, after the connection is established.

Greetings,

scoonma

Hi michael,

you'll probably need the phython developer's package(s). Please try an "urpmi libpython2.4-devel" first.

When building software manually, this is a rather common situation. In these cases, look out for "xyz-devel" or "libxyz" packages. urpmf is your friend. :-)

HTH,

scoonma

Well, maybe you *can* explore, but in this case chances are very good to get lost...

Hi seraph,

great site! however, i have one problem. when i run this: $ cat /proc/acpi/processor/CPU0/throttling, i get this: <not supported>. :(

You can "cd /proc/acpi/processor/CPU0" and cat the different entries to get some information.

strange to me since Windows seems to throttle my CPU just fine. When I run in Linux, my fans are running constantly and it heats up very quickly. Then, when i boot into windows, after about 1 mins, it is cooler to the touch and blowing cooler air out of the computer. Obviously windows is doing something right and Linux is doing something wrong.

But do you know which technical means Win is using in order to achieve this? ;-)

Serious: It can be alluring to try (some or many) different software to achieve your goal if the first one does not work. But this is a rather Window-ish style to deal with problems. In the long run you'll get much more fun if you 1. Check if a software is capable of solving your problem and 2. Learn the usage and options to work with the soft appropriately. I'm not into talking you to stick to cpufreq, but please note that functioning relies on the latter (you've already read the cpudyn FAQ, right?).

Good luck,

scoonma

Hi seraph,

you could adjust a profile to use the slowest freqency possible, then clock boot time (after cpufreqd being loaded). This is no elegant solution, but should work.

HTH,

scoonma