Slackware :: Eth0 No Longer Recognized After Upgrade And ASUS Mobo Replace In -current
Jan 27, 2010
My office has a box which is, by necessity, dual-boot WinXP/Slack. The Slackware I'm running there is -current, all great and fine. Until now... It turned out that my mobo, an ASUS P5KPL-CM, died after a power surge. Since the XP needs software activation, we replaced it for an exact copy of the mobo. After the change the box worked fine in XP, and I was able to connect to the network via the Ethernet interface. BTW, the Slackware version is Slackware-current, updated as of the Jan 9 update (after that I was no longer able to connect to the Net with Slack). However, in Slackware there was a problem: eth0 was no longer recognized. Using /sbin/ifconfig only listed the lo (loopback) interface. The lspci output is:
i was using ubuntu netbook remix and works......but presents problems with the gma500 chipset, and with some poulsbo packages works better, but without composite or some compiz efect, and not really fluid. with jolicloud is the same, but much better.
Anyone have this netbook with slack? using any desktop?? the support for the gma500 in slack is... im in investigation time to resolv wich distro is the best for my netbook. In my desktop always rules slackware je
I have some tools that seem to have issues with Python 2.5 but are OK (on other systems) with Python 2.6. So, I was considering upgrading my Python interpreter to the current 2.6.4, but I know that in various RH distros, this was strongly discouraged. Is it OK to replace my current Python 2.5.2 on F10? If so, should that be done from source or can I do this cleanly through yum?
In Slackware current there's a problem where iptraf does not show eth0. Here's a link to the bug report and patch.
[URL]
[URL]
I've had this show on 2 different current PCs. Kernels 2.6.35.10 and 2.6.35.7. This is with an Atheros AR8121/AR8113/AR8114, and Realtek RTL8111/8168B.
I stuck a flash drive into a usb port this morning, and the device notifier failed to show. I opened Dolphin, and I noticed that nothing that should be mounted was showing up in the left pane. I always have seen my Windows install, as well as another partition that has Slackware. I can navigate to /mnt/vista and its all there. I can also go to /mnt/Slackware and its all there. However, the flash drive does not show.I can manually mount the drive and all is well as root. I can't even tell you when this started. I am using Alien's 4.6 KDE packages with all the deps. I just opened mc and checked everything. HAL is disabled and has been for a long time. All did work after disabling HAL.Its not just the flash drive, it effects anything - music cds, blank media, nothing works automagically. Google hasn't
I'm about to add pci ethernet card. Currently the mobo nic is eth0. When I add the new card will it by definition be eth1 (or will it become eth0 and the mobo nic become eth1)? The broader question is: how are the "eth's" numbered at boot time? If I were to add a 2nd pci nic, could I predict which would be eth1 and which would be eth2 (based on pci slot number??)? Is there somewhere to readup on this to get a broader understanding?
Got an Asus eeepc 900a. Runs Intel 915 graphics. Upgraded to slackware current last week. X would not start. Based on info here, I reverted back to earlier libdrm and xf86-video-intel. That got it working again.
Updated Slackware current again today. I think I got a new kernel. Now, halfway through boot time, the screen goes blank, then comes back and the font is tiny. Gone into framebuffer mode. If I start X, it just freezes. Nothing but a reboot will get out of it.
I have vga=normal in lilo.conf, but I read that this is no longer used. I can find no way to turn off framebuffer mode. From other threads here, I have tried append="i915.modeset=1" in lilo.conf. Has no effect.
I could revert Slackware to 13.0 from current, and that would make the eeepc useful again. Is there anything else I should try?
I have 10.04 LTS installed onto an SSD and have a spinning disk for crud, and my brother wants to give me his old GA-PH67A-UD3 and 8GB of RAM if I buy an i7 2600 to put in it. The thing is, I'm happy with my GA-965P-DS3 with Q6600, so I don't actually need an upgrade. So, can I get away with replacing the mobo, chip, and RAM and putting the SSD in the equivalent SATA port on the new mobo (/dev/sda), and will it cope? Will the kernel detect a new board and chip and carry on accordingly? I'll have to remount my crud drive to the same mount point it expects, and if my user account as the same UID as the old system, I'm hoping that might cope, too. Of course, I might be suggesting complete evil, and if this was Windows, I wouldn't even dare think about it, but I have a sneaking suspicion that Linux might cope with this kind of change where Windows would fall over in a heap.
I just purchased a new PC with the following specs:
Intel Core i5-760 ASUS P5P55D-E LX (S1156 mobo) Sapphire HD 5750 Vapor-X 1GB Video Card Samsung 1TB HDD Corsair DDR3 PC1333 Gaming RAM - 2x2GB DVD: Samsung DVD burner (internal)
I have made several trials to install Lucid Lynx but all failed:
1. Installed Windows 7 64-bit, hdd formatted as NTFS and ext3, then trying to install Lucid Lynx 32-bit : failed.
2. Installed Windows XP 32-bit, hdd formatted as FAT32, then trying to install Lucid Lynx 32-bit : failed.
3. Trying to install Lucid Lynx 32-bit with a clean hdd formatted as FAT32: failed.
In all the scenarios above, I have tried using Ubuntu installers on CD, DVD, or USB. on CD and DVD, the process always stopped after the Ubuntu logo screen, not even reached the langauage selection screen. On USB, with Legacy set to On in the BIOS, it did run and started by the option screen where we get to choose booting from the usb, or booting from hdd, or memory test, etc., but after choosing the booting from usb (and then hdd also) option, the process also stopped after the Ubuntu logo screen. I have experience dual booting Windows XP with Lucid Lynx on an older system, so I'm not completely new in this. I'd like to know what actually went wrong?
How can I convert eth1 back into eth0 on Fedora 13? I searched /etc for eth1 and found it in 70-persistent-net.rules, but eth0 is still in the ifcfg scripts.
I recently upgraded to slackware-current from Slackware 13 via slackroll, and have only encountered one problem. My file manager no longer thumbnails images, and icons (mostly PNG) aren't appearing no matter what GTK theme is set. Running from the command line produces no errors, and when brought up in something else (say feh /path/to/icon.png) it works perfectly. This is the only hitch I have encountered so far. The same thing happens with emoticons in Pidgin. Does anyone know of a fix?
One partition of my pata drives is not recognized anymore after upgrade. Using fdisk the partition is seen but just 33,8 GB of the 205 GB drive is recognized at all.
Quote:
root@7of9:~ >>> /sbin/fdisk -l /dev/sdd Disk /dev/sdd: 33.8 GB, 33820286976 bytes 255 heads, 63 sectors/track, 4111 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
[code].....
The filesystem is ok. Booting Slackware 12.2 the partition is recognized and mountable. why /dev/sdd4 is not recognized by Slackware 13.1?
Is there any chance we'll see the newer version of Audacious (2.4.2) in -current, or is it too late in the day? If I get time, I may try building it on my -current install.
i can start X with the nvidia module, the log here:
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/slacker:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 X.Org X Server 1.7.5 Release Date: 2010-02-16
I'd have said SNAFU, but the truth is that I really don't recall this mess being "normal" in Slackware since v7. This kind of mess is what I expect from Ubuntu, not Slack. Here's what happened. I was running Slackware-Current 12/10/10 and wanted to move up to Current 1/10/11. I read and followed the UPGRADE.txt including running "telinit 1". The system had 2 working kernels menued in Lilo, a custom 2.6.35.10 symlinked to "/boot/vmlinuz", and a custom 2.6.36 fully declared in lilo.conf and labelled Current.
The "upgradepkg --install-new" installed a "new" kernel which would only have required a simple deletion, but somehow and for some silly reason my lilo.conf was overwritten and lilo run so that when I selected "Current" instead of my nice 2.6.36, long story short, I got a badly working kernel where my keyboard didn't work.
Why would "upgradepckg --install-new" install an older kernel, and more importantly, instead of merely as an added option, override and ruin my existing, working lilo? Slax is overhauling to add pacman and I see some people even here leaning toward more automated package management in Slackware. What gives? Is Slackware headed down this path? Please, Joe, just tell me it ain't so.
I've (almost successfully) upgraded my 64-current.
1. It used to be or is? 64-current multilib, however, before the upgrade I commented out any blacklisted packages in slackpkg's blacklist file (including aaa_eflibs)
slackpkg update, install-new, upgrade-all, clean system (removed all the packages that were specified in changelogs.txt as removed)
When started X two things were wrong.
1. XFCE icons disappeared
2. The mouse pointer was going crazy
2. I fixed it by following Eric's advice and created a file in /etc/X11/xorg.conf.d/20-mouse.conf where I put the Input section from my xorg.conf
I'm still at loss when it comes to the icons.
btw, I've reinstalled my nvidia binary blob, somehow it doesn't seem to see it. Does the new Xorg use xorg.conf anymore?
I'm using Slackware current. I've updated my current after about two months from the last update, and since there was a huge number of changes I'm having some problems. In particular, I've forgot (my fault!) to give a "slackpkg install-new" before rebooting, so now I'm getting stuck...
Installpkg now claims a "rev" command, but I cannot figure how to find it, since the Slackware package browser on the website is still broken (when will it be available?!?!). Now, each time I try to install or upgrade a new package, I get this error:
/sbin/upgradepkg: line 41: rev: command not found /sbin/installpkg: line 59: rev: command not found
First: I upgraded my slackware 13.0 last night (Philippine time) to -current. I just download the while current tree (except for source) and copied to my home dir, then do the slackpkg commands.
#1 Added a mirror to my home directory pointing the slackware-current tree. #2 slackpkg update #3 slackpkg install-new #4 slackpkg upgrade-all #5 slackpkg clean-system #6 lilo was configured #7 reboot
It successfully upgraded. Although I'm aware that I have installed openchrome driver and drm kernel module when it was slackware 13.0.
After a reboot, it crashes in between the boot time, if I was not mistaken, I read ACPI something on the bottom of the console, then the screen flickers and goes blank. It locks up there.
By the way, it is a laptop with VIA chipset on it.
(Using the Slackware 13.0 DVD, I booted using hugesmp.s root=/dev/sda3 rdinit= ro for the rescue.)
Trying to fix it by myself (no internet at home) I tried to look at /var/log/messages and cannot find what is the cause (newbie mode). I also tried to disable some services such as hald, httpd, mysqld, bluetooth, wicd, wireless, the old kernel and some others at /etc/rc.d/ by removing the execute bit.
After a restart, still the problem exists.
Now, I finally backup the whole home dir, moved to home-bak and decided to install the fresh slackware-current instead.
Second: I used the 13.0 installer, then setup slackware using the pre-mounted directory containing the slackware-current tree. I only deleted the files except for home-bak and not reformat the drive.
It actually installs, but after the reboot (using the new 2.6.32.3 kernel), still the problem persists.
I recently upgraded my -current box, and now when I try to run sbopkg I get the exact error described in the following thread:[URL].. The error fwiw is as follows:
root@catbutt:~# sbopkg ERROR sbopkg: Invalid repository descriptor Line SBo 13.0 "SBo repository for Slackware 13.0" _SBo rsync slackbuilds.org::slackbuilds/13.0 GPG of /etc/sbopkg/repos.d/40-sbo.repo specifies an unknown fetching tool (rsync).
seems likely given the discussion in that previous thread that the bash upgrade (to 4.1.002) in the recent -current onslaught is responsible?
I'm about to attempt to upgrade gtk+2 from the current 2.14 to 2.16 to fulfill a requirement for devede, I'm planning on using the slackbuild from slackware/l/gtk+2 and just editing the version. I think this approach will work but I was hoping to get some feedback (and any warnings or advice) before I dive in - obviously I will back up before hand.
I thought I would try out Eric's KDE 4.5.1 and Robby's new Xorg pacakges. The upgrade went off with out a hitch, but now when I try to launch conky I get
conky: error while loading shared libraries: libmowgli.so.1: cannot open shared object file: No such file or directory
So I rebuilt conky and reinstalled libmowgli ran ldconfig but I still get the error.
After upgrading to -current (using slackpkg), my touchpad scrolling won't work.I remember that this had solved my problem previous time and in fact, after upgrade I have changed nothing (since this file already existed there). When I check the /usr/share/hal/fdi/ policy/ 10osvendor/ directory, I see that no "11-x11-synaptics.fdi" file was present. I just copied the file from /etc/hal/fdi/policy into this directory, but this did not help. Can somebody guide me through this?
After the updates galore of yesterday in -current, I began to update my system using slackpkg. However, after upgrading the kernel packages, I had a power problem and the system went down. (I had run lilo first, before the blackout happened) Upon powering it on again, my system won't boot. The kernel loads, and then init takes control, but when it comes to the regular fsck, the boot halts with a big, scary warning message that the filesystem might have an error and libblkid.so.1 is missing.
Be advised that the packages in the big update of yesterday were installed on alphabetical order. An inspection on the Jan 25-updated version of Slackware-current on my laptop reveals that the library in question is part of e2fsprogs. That's odd; if there was an update for it, it should already have been installed, but the system complains that a file from that package is missing, anyway. All this boils down to: my system is now unusable, unable to boot, and I really don't have a clue on what to do.
I am running -current on an ASUS eeePC 1000HE. Wireless was working fine up until the time I applied the latest changes from the Slack -current tree, which upgraded wpa_supplicant. Now, no networks are detected.
I looked at some related threads here and did some basic checking: neither the eth1 nor wlan0 interfaces show up in iwconfig or ifconfig output. Am afraid I am still a wireless dunderhead and don't know where to start troubleshooting this issue.
After upgrade to ghostscript 9.02 from current all print jobs fail with: 'There is a missing print filter for printer HP_F2480'
The printer is an All-inone deskjet F2480 and the cups printer queue has been setup with the hplip tools. Before the upgrade it was 'working' with quite a few bugs...eg image not printed correct, multipage printing garbage. (page for page printing was the workaround)
Do I need to remove the printer and define it again?
I have an old system, and want to upgrade the MOBO and processor. I am running Ubuntu 10.04 32bit...If I upgrade the MOBO and CPU to a 64 bit system....what will happen?
My Asus k52 BBR9 was working great with Meerkat until I put in all the updates.Now it won't recognize my wireless: it says were connected and the icon is clear or it is dark or has the icon look pulsing where there is my connection. But I can't get online.
OS Version: CentOS 5.3 Motherboard: ASUS M3A78-CM (BIOS v.2003)
I have a single disk running the base OS and just installed 2 x Seagate 500GB SATA 3.0 drives in a RAID1 set that I would like to use for data storage. The OS sees the drives individually but not the RAID. Has anyone worked with a similar board and has any ideas what I need to do to get the OS to recognize the RAID1 array?
just installed opensuse 11.3 on my asus eee pc 1018p and have severe problems to make the wireless network card work. tried to install the driver with ndiswrapper and b43-cutter, but without any success. ifconfig does not show any wlan0 device. below find output of
lspci -v dmesg ifconfig
installed opensuse on several notebooks/netbooks before but never ran into serious trouble.
