Arch problemen

[filenox]

Dit is een vervolg op deze problemen

Grub is opnieuw geinstalleerd,dus het moet aan het configbestand liggen
Ik heb 1HD,met 3partities; SDA1 (Windows) - SDA2 (Arch) - SDA3 (SWAP)

Dan dat netwerkprobleem,
Hier vind ik niks fout in

# /etc/rc.conf - Main Configuration for Arch Linux
#

#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
TIMEZONE="Canada/Pacific"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

#
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=()
#
# Modules to load at boot-up (in this order)
# - prefix a module with a ! to blacklist it
#
MODULES=(8139too mii)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="myhost"
#
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available
# interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(lo eth0)
#
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
#
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network-profiles
#
#NET_PROFILES=(main)

#
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng network netfs crond)


# End of file

[Drgn]

Op de Arch pagina staat best al veel info.

Verbinding maken met internet staat stapsgewijs in algemene stappen uitgelegd:

Internet Access

Due to a lack of developers for dialup issues, connecting Arch to the
Internet with a dialup line is requiring a lot of manual setup. If at
all possible, set up a dedicated router which you can then use as a
default gateway on the Arch box.

There are quite a few dialup related documents in the Arch Linux Wiki

Analog Modem

To be able to use a Hayes-compatible, external, analog modem, you need
to at least have the ppp package installed. Modify the file
/etc/ppp/options to suit your needs and according to man pppd. You
will need to define a chat script to supply your username and passwort
to the ISP after the initial connection has been established. The
manpages for pppd and chat have examples in them that should suffice
to get a connection up and running if you're either experienced or
stubborn enough. With udev, your serial ports usually are /dev/tts/0
and /dev/tts/1.

Instead of fighting a glorious battle with the plain pppd, you may opt
to install wvdial or a similar tool to ease the setup process
considerably.

In case you're using a so called WinModem, which is basically a PCI
plugin card working as an internal analog modem, you should indulge in
the vast information found on the LinModem homepage.

ISDN

Setting up ISDN is done in three steps:
1. Install and configure hardware
2. Install and configure the ISDN utilities
3. Add settings for your ISP

The current Arch stock kernels include the necessary ISDN modules,
meaning that you won't need to recompile your kernel unless you're
about to use rather odd or old ISDN hardware. After physically
installing your ISDN card in your machine or plugging in your USB
ISDN-Box, you can try loading the modules with modprobe. Nearly all
passive ISDN PCI cards are handled by the hisax module which needs two
parameters; type and protocol. You must set protocol to '1' if your
country uses the 1TR6 standard, '2' if it uses EuroISDN (EDSS1), '3'
if you're hooked to a so called leased-line without D-channel, and '4'
for US NI1.

Details on all those settings and how to set them is included in the
kernel documentation, more specifically in the isdn subdirectory,
available online. The type parameter depends on your card; A list of
all possible types is to be found in the README.HiSax kernel
documentation. Choose your card and load the module with the
appropriate options like this:
# modprobe hisax type=18 protocol=2

This will load the hisax module for my (Dennis) ELSA Quickstep
1000PCI, being used in Germany with the EDSS1 protocol. You should
find helpful debugging output in your /var/log/everything.log file in
which you should see your card being prepared for action. Please note
that you will probably need to load some usb modules before you can
work with an external USB ISDN Adapter.

Once you confirmed that your card works with certain settings, you can
add the module options to your /etc/modprobe.conf:
alias ippp0 hisax
options hisax type=18 protocol=2

Alternatively you can only add the options line here, and add hisax to
your MODULES array in the rc.conf. Your choice, really, but this
example has the advantage that the module will not be loaded until
it's really needed.

That being done you should have working, supported hardware. Now you
need the basic utilities to actually use it!

Install the isdn4k-utils package, and read the manpage to isdnctrl,
it'll get you started. Further down in the manpage you will find
explanations on how to create a configuration file that can be parsed
by isdnctrl, as well as some helpful setup examples.

Please note that you have to add your SPID to your MSN setting
seperated by a colon if you use US NI1.

After you configured your ISDN card with the isdnctrl utility, you
should be able to dial into the machine you specified with the
PHONE_OUT parameter, but fail the username and password
authentication. To make this work add your username and password to
/etc/ppp/pap-secrets or /etc/ppp/chap-secrets as if you were
configuring a normal analogous PPP link, depending on which protocol
your ISP uses for authentication. If in doubt, put your data into both
files.

If you set up everything correctly, you should now be able to
establish a dialup connection with isdnctrl dial ippp0 as root. If you
have any problems, remember to check the logfiles!

DSL (PPPoE)

These instructions are only relevant to you if your PC itself is
supposed to manage the connection to your ISP. You do not need to do
anything but define a correct default gatewayif you are using a
seperate router of some sort to do the grunt work.

Before you can use your DSL online connection, you will have to
physically install the network card that is supposed to be connected
to the DSL-Modem into your computer. After adding your newly installed
network card to the modprobe.conf or the MODULES array, you should
install the rp-pppoe package and run the pppoe-setup script to
configure your connection. After you have entered all required data,
you can connect and disconnect your line with
# /etc/rc.d/adsl start

and
# /etc/rc.d/adsl stop

respectively. The setup usually is rather easy and straightforward,
but feel free to read the manpages for hints. If you want to
automatically dial in on bootup, add adsl to your DAEMONS array.

Over Grub, je zei eerst dat je niet in Arch kwam, toen heb je Grub ge(her)ïnstalleerd en nu kom je niet meer in Windows, correct?
Had je die Grub her-install via deze guide gedaan or anders? Krijg je misschien nog een foutmelding die je met ons wilt delen?

[filenox]

tutorial had ik al gevonden,maar ik snap er niet echt veel van

Over Grub, je zei eerst dat je niet in Arch kwam, toen heb je Grub ge(her)ïnstalleerd en nu kom je niet meer in Windows, correct?
Had je die Grub her-install via deze guide gedaan or anders?

Ik heb "nu" een format gedaan (ext3-format)
En nu graak ik wél in Arch,zonder netwerkverbinding
Maar niet in Windows

[Drgn]

tutorial had ik al gevonden,maar ik snap er niet echt veel van

ow


Ennûh, wat snap je dan niet? Nog meer uitleg.
Oh ja, en (1) je vertelt nog steeds niet of je een foutmelding krijgt bij het booten en (2) hoe je grub opnieuw hebt geïnstalleerd.

[Jungian]

Doritos schreef op dinsdag 15 mei 2007 @ 16:20:
En nu graak ik wél in Arch,zonder netwerkverbinding

Je weet zeker dat je statisch je ip wilt vaststellen ?

code:

eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"

dus (zoals het er nu staat) ?
En

code:

gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

mag je uitcommenten.

[filenox]

uitcommenten = verwijderen ?

[Creepy]

Als je instellingen van het netwerk kloppen moet je die regels niet (uit)commenten! Je moet dan alleen de uitroepteken voor gateway weghalen zodat de gateway ook daadwerkelijk wordt ingesteld.

code:

gateway="default gw 192.168.0.1"
ROUTES=(gateway)

Zo dus.

[ Voor 16% gewijzigd door Creepy op 16-05-2007 14:08 ]

[Jungian]

Doritos schreef op woensdag 16 mei 2007 @ 14:05:
uitcommenten = verwijderen ?

Nee. Kijk naar de rest van het document en het lijkt me vrij duidelijk hoe je ergens commentaar van maakt (tip : #).

[blaataaps]

Nee, en wat het wel is wel te vinden op google. En "ik snap het niet" en "het werkt niet" kunnen wij helemaal niks mee wat debuggen betreft, we verwachten hier wel enige zelfredzaamheid, en ik wil je ten slotte nog verzoeken geen underline meer te gebruiken om iets te benadrukken, maar bijvoorbeeld italic, bold, of gewoon helemaal niks.