jethro Posted January 27, 2006 Report Share Posted January 27, 2006 Hi everybody, I'm forced to boot with the "noapic" option, because else my networkcard hangs on high speeds (above ~ 4 MB/s). Before the "noapic" boot-option the following line in my fstab worked fine: //ephyra.jesdesign.nl/jdhd /home/jethro/jdhd smbfs user,username=jethro,password=xyz,uid=jethro 0 0 But now it gives this error: Jan 27 10:31:05 Jethro haldaemon: haldaemon startup succeededJan 27 10:31:05 Jethro mount: 2620: Connection to ephyra.jesdesign.nl failed Jan 27 10:31:05 Jethro mount: SMB connection failed Jan 27 10:31:05 Jethro netfs: Mounting SMB filesystems: failed Jan 27 10:31:05 Jethro netfs: Mounting other filesystems: succeeded Does anybody know why it doesn't work anymore since the "noapic" option is forced when booting? Thanks in advance. Best regards, Jethro Quote Link to comment Share on other sites More sharing options...
Qchem Posted January 27, 2006 Report Share Posted January 27, 2006 Does the network card come up before the filesystems are mounted? Quote Link to comment Share on other sites More sharing options...
jethro Posted January 27, 2006 Author Report Share Posted January 27, 2006 This is my entire boot.log file: Jan 27 10:31:03 Jethro partmon: Checking if partitions have enough free diskspace: Jan 27 10:31:03 Jethro partmon: ^[[65G[^[[1;32m Jan 27 10:31:03 Jethro partmon: Jan 27 10:31:03 Jethro rc: Starting partmon: succeeded Jan 27 10:31:03 Jethro acpid: acpid startup succeeded Jan 27 10:31:03 Jethro nfslock: rpc.statd startup succeeded Jan 27 10:31:04 Jethro sound: Setting mixer settings succeeded Jan 27 10:31:04 Jethro xfs: xfs startup succeeded Jan 27 10:31:04 Jethro messagebus: messagebus startup succeeded Jan 27 10:31:05 Jethro haldaemon: haldaemon startup succeeded Jan 27 10:31:05 Jethro mount: 2620: Connection to ephyra.jesdesign.nl failed Jan 27 10:31:05 Jethro mount: SMB connection failed Jan 27 10:31:05 Jethro netfs: Mounting SMB filesystems: failed Jan 27 10:31:05 Jethro netfs: Mounting other filesystems: succeeded Jan 27 10:31:05 Jethro numlock: Jan 27 10:31:06 Jethro rc: Starting numlock: succeeded Jan 27 10:31:06 Jethro dm: Display manager startup succeeded Jan 27 10:31:09 Jethro mDNSResponder: startup succeeded Jan 27 10:31:09 Jethro atd: atd startup succeeded Jan 27 10:31:10 Jethro sshd: startup succeeded Jan 27 10:31:10 Jethro rawdevices: succeeded Jan 27 10:31:10 Jethro xinetd: xinetd startup succeeded Jan 27 10:31:10 Jethro loadkeys: Loading /usr/lib/kbd/keymaps/i386/qwerty/us-intl.kmap.gz Jan 27 10:31:10 Jethro keytable: Loading keymap: us-intl succeeded Jan 27 10:31:10 Jethro loadkeys: Loading /usr/lib/kbd/keymaps/include/compose.latin9.inc.gz Jan 27 10:31:10 Jethro keytable: Loading compose keys: compose.latin9.inc succeeded Jan 27 10:31:10 Jethro keytable: succeeded Jan 27 10:31:11 Jethro freshclam: freshclam startup succeeded Jan 27 10:31:11 Jethro crond: crond startup succeeded Jan 27 10:31:12 Jethro smb: smbd startup succeeded Jan 27 10:31:12 Jethro smb: nmbd startup succeeded Jan 27 10:31:13 Jethro lisa: Starting lisa: succeeded Jan 27 10:31:13 Jethro rc: Starting kheader: succeeded There is nothing in there about bringing up de eth0 interface. There was before the noapic booting option. Before that I coulde see the eht0 coming up. How can I force it to go up before the execution of fstab? Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted January 27, 2006 Report Share Posted January 27, 2006 Check in the following directory: /etc/sysconfig/network-scripts there should be a file called ifcfg-eth0 or something along those lines unless you have more than one nic, then eth1 etc, etc. Now, type: cat ifcfg-eth0 there should be an option like onboot=yes. If it is set to "no", then this will be why your network isn't starting. Here is my ifcfg-eth0 file: [ian@europa ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO=static IPADDR=xx.xx.xx.xx NETMASK=xxx.xxx.x.x NETWORK=xxx.xx.x.x BROADCAST=xxx.xx.xxx.xxx ONBOOT=yes HWADDR=xx:xx:xx:xx:xx:xx METRIC=10 MII_NOT_SUPPORTED=no USERCTL=no IPV6INIT=no IPV6TO4INIT=no PEERDNS=yes I've replaced sensitive data with xx:xx:xx on purpose, this would normally read my IP details and MAC address. Quote Link to comment Share on other sites More sharing options...
jethro Posted January 27, 2006 Author Report Share Posted January 27, 2006 Here is my file: [jethro@dhcppc3 network-scripts]$ cat ifcfg-eth0DEVICE=eth0 BOOTPROTO=dhcp NETMASK=255.255.255.0 ONBOOT=yes HWADDR=00:a0:d1:29:38:df METRIC=10 MII_NOT_SUPPORTED=no USERCTL=yes IPV6INIT=no IPV6TO4INIT=no PEERDNS=yes NETMASK=255.255.255.0 DHCP_CLIENT=dhclient NEEDHOSTNAME=yes PEERDNS=yes PEERYP=no PEERNTPD=no As you can see the "ONBOOT" option is already set properly... Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted January 27, 2006 Report Share Posted January 27, 2006 Just out of interest, if you configure for a static ip address, rather than DHCP, does it work any better? Also, I see that it lists a netmask, but normally this is picked up by DHCP, so I'm a little confused by the settings in this file. First, try allocating a static ip address, and see if everything starts to behave normally. If you cannot allocate a static ip address for one reason or another, then delete the ifcfg-eth0 file, then reboot, and then reconfigure your eth0 interface using MCC/Configure Your Computer. Alternatively, to save the reboot you can do this: ifdown eth0 rm /etc/sysconfig/network-scripts/ifcfg-eth0 (choose yes when prompted) reconfigure using MCC/Configure Your Computer I have a funny feeling, that some settings here are a little messed up. Quote Link to comment Share on other sites More sharing options...
jethro Posted January 27, 2006 Author Report Share Posted January 27, 2006 (edited) I think you're right, but now I've messed them up even more. I've deleted al the ifcfg-* files. That's stupid of me, I know, because now Mandriva will not boot anymore. I get passed all the screen until the end when it has to display my desktop, then it just hangs. I can still use my mouse, but that's all I can do...... Is there a way to get the ifcfg-* files back? After removing all the if-cfg* files I made a new network interface and that seemed to work. So i decided to reboot to check if fstab was working fine to and then I discovered that it wil not boot anymore. At boottime there is an error about if-cfg-lo (or something like that) missing. After that it hangs on "Starting SMB services". Edited January 27, 2006 by jethro Quote Link to comment Share on other sites More sharing options...
scarecrow Posted January 27, 2006 Report Share Posted January 27, 2006 Reinstall, and next time be careful after you type "su". Quote Link to comment Share on other sites More sharing options...
jethro Posted January 27, 2006 Author Report Share Posted January 27, 2006 Reinstall, and next time be careful after you type "su". <{POST_SNAPBACK}> Your not serious are you? It took me so much work to make this install work the way it does now. I don't have a lot of experience with Mandriva and because of new hardware issues it took a long time to make it work. Isn't there a way to just put the deleted file if-cfg-lo (or something like that) back? Quote Link to comment Share on other sites More sharing options...
scarecrow Posted January 27, 2006 Report Share Posted January 27, 2006 (edited) Your not serious are you? It took me so much work to make this install work the way it does now. It also took you a few seconds to delete initscripts... How can you put them back on an unbootable system? You cannot even access a trashbin... "Isn't there a way to just put the deleted file if-cfg-lo (or something like that) back?" means that you actually do not even know what exactly you have deleted! If at the first LILO screen you press escape and then type linux 1 ...you will likely get a single user login and eventually be in, but then fixing what? Even at the point you get the mouse pointer alt+ctrl+backspace may bring a console login, but then again there's nothing to fix without knowing what's broken. Edited January 27, 2006 by scarecrow Quote Link to comment Share on other sites More sharing options...
jethro Posted January 27, 2006 Author Report Share Posted January 27, 2006 When booting with "linux init 3" and looking at the log messages I see this: Bringing up loopback interface: ./ifup: configuration for ifcfg-lo no found. Usage: ifup <device name> I managed to login with linux init 3 and then I copied ifcfg-lo back. Right now I'm back at the same spot where I was at the beginning of this thread, fstab doens't work anymore since I had to boot with the noapic boot option... Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted January 27, 2006 Report Share Posted January 27, 2006 OK, is your ifcfg-eth0 file looking any better now than it was before? Set up for DHCP or Static? Quote Link to comment Share on other sites More sharing options...
jethro Posted January 27, 2006 Author Report Share Posted January 27, 2006 (edited) Right now I configured eht0 to be static and it works fine with fstab. Here is the content of ifcfg-eth0: DEVICE=eth0BOOTPROTO=static IPADDR=10.0.0.157 NETMASK=255.255.255.0 NETWORK=10.0.0.0 BROADCAST=10.0.0.255 ONBOOT=yes HWADDR=00:a0:d1:29:38:df METRIC=10 MII_NOT_SUPPORTED=no USERCTL=yes IPV6INIT=no IPV6TO4INIT=no PEERDNS=yes I would really like to make it work with DHCP though, because tthis is all working on a laptop which I use at various different locations. Edited January 27, 2006 by jethro Quote Link to comment Share on other sites More sharing options...
Qchem Posted January 28, 2006 Report Share Posted January 28, 2006 Just after booting (when attempting to use dhcp) use dmesg to see the kernel messages, it may be worth comparing this with the same output from your statically set IP address. If you want to save the dmesg output for later, you could do something like: dmesg > ~/dmesg-dhcp.log Note, contrary to what an earlier poster said, always go for a reinstall as a very last measure - almost everything can be fixed that you can break in Linux. Quote Link to comment Share on other sites More sharing options...
jethro Posted January 28, 2006 Author Report Share Posted January 28, 2006 dmesg doesn't report anything about the booting from fstab. This is what is says about eth0: [jethro@jethro ~]$ dmesg | grep etheth0: RealTek RTL8139 at 0xdcec6000, 00:a0:d1:29:38:df, IRQ 11 eth0: Identified 8139 chip type 'RTL-8100B/8139D' eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 eth0: no IPv6 routers present Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.