LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 07-15-2012, 05:09 PM   #91
BroX
Member
 
Registered: Oct 2003
Location: Sweden
Distribution: Slackware64-current
Posts: 759

Rep: Reputation: 65

Quote:
Originally Posted by Woodsman View Post
Yes, init 3 is the default. We're talking about how recent changes in the util-linux package now change the default to clearing the screen after the init process ends.
...
Sorry, my bad Thanks for explaining!
 
Old 07-15-2012, 05:12 PM   #92
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,274

Rep: Reputation: 587Reputation: 587Reputation: 587Reputation: 587Reputation: 587Reputation: 587
Code:
+--------------------------+
Sun Jul 15 01:40:08 UTC 2012
Juggle a few things around so that slackpkg won't fall over while upgrading
from 13.37 or an earlier -current:
I can report that slackpkg works properly again when you upgrade from Slackware 13.37 or an earlier version of -current. I did a clean install of 13.37 (32 bit) and then used slackpkg to upgrade to slackware-current. Upgrade proceeded normally.
 
Old 07-15-2012, 05:13 PM   #93
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,575

Rep: Reputation: 466Reputation: 466Reputation: 466Reputation: 466Reputation: 466
Quote:
Would it be possible to list all the removed packages and all the added packages at the start of the changelog?
Well, you'd have to narrow down the part of the changelog that contains the update but the command...
Code:
grep -e "^.\\{1,4\\}/" name_of_file_containing_changelog_subset | sort -k2 | grep -e "\\(Added\\|Removed\\)\\.$"
...gives you the same information.

The first grep removes everything that doesn't appear to be a package name line, the sort uses the 2nd field as defined by whitespace to sort, and the last grep gives you every line that ends with either "Added." or "Removed.".

You could certainly combine the two greps into one and do that one prior to the sort, if you wish.
 
Old 07-15-2012, 05:14 PM   #94
audriusk
Member
 
Registered: Mar 2011
Location: Klaipėda, Lithuania
Distribution: Slackware
Posts: 248

Rep: Reputation: 107Reputation: 107
Quote:
Originally Posted by ruario View Post
Code:
wget -qO- ftp://ftp.slackware.com/pub/slackware/slackware-current/ChangeLog.txt | grep ':  Removed\.$'
Code:
wget -qO- ftp://ftp.slackware.com/pub/slackware/slackware-current/ChangeLog.txt | grep ':  Added\.$'
Or grep /var/lib/slackpkg/ChangeLog.txt after running slackpg update. I have this alias in my .bashrc for convenience:
Code:
alias changelog='less /var/lib/slackpkg/ChangeLog.txt'
 
Old 07-15-2012, 05:27 PM   #95
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Linux Mint 17.1
Posts: 1,424

Rep: Reputation: 137Reputation: 137
Kind thanks to celyr, ruario, Richard Cranium, and audriusk for answering my post about listing added and removed packages at the beginning of the changelog.

I personally follow the method used by celyr, however it occurred to me that if these added/removed packages were more prominently marked in the changelog then there would be less threads that start, "I just upgraded my system and this broke/happened/wouldn't compile etc."

So my post was a constructive comment for consideration rather than a cry for help.

Thanks again.

samac
 
Old 07-15-2012, 05:43 PM   #96
AlleyTrotter
Member
 
Registered: Jun 2002
Location: Coal Township PA
Distribution: Slackware64-14.1 (3.18.0) UEFI enabled
Posts: 360

Rep: Reputation: 77
eager beaver

Quote:
Originally Posted by samac View Post

So my post was a constructive comment for consideration rather than a cry for help.

Thanks again.

samac
So many "eager beavers"
I just love the way there are so many people anxious to help on this forum
No disrespect intended
John
 
Old 07-15-2012, 06:08 PM   #97
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,902

Rep: Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963
@samac: Just for fun (I saw your post saying you use slackpkg, so I know it is not for you), this would give you a one line list of packages that have been removed:

Code:
wget -qO- ftp://ftp.slackware.com/pub/slackware/slackware-current/ChangeLog.txt | sed -nr 's#.*/([[:graph:]]+)(-[[:alnum:]\.\+_]+){3}\.t.z:  Removed\.$#\1#p' | tr '\n' ' '; /bin/echo -ne '\n'
Assuming it all looked OK, they could be removed with:

Code:
wget -qO- ftp://ftp.slackware.com/pub/slackware/slackware-current/ChangeLog.txt | sed -nr 's#.*/([[:graph:]]+)(-[[:alnum:]\.\+_]+){3}\.t.z:  Removed\.$#\1#p' | xargs -d'\n' removepkg
Quote:
Originally Posted by AlleyTrotter View Post
So many "eager beavers"
I just love the way there are so many people anxious to help on this forum
No disrespect intended
John
None taken

Last edited by ruario; 07-16-2012 at 03:03 AM. Reason: Added reply to AlleyTrotter; improved regex after inspecting PACKAGES.TXT
 
1 members found this post helpful.
Old 07-15-2012, 06:35 PM   #98
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,902

Rep: Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963
Quote:
Originally Posted by samac View Post
it occurred to me that if these added/removed packages were more prominently marked in the changelog then there would be less threads that start, "I just upgraded my system and this broke/happened/wouldn't compile etc."
Even though I am one of the ones who replied, it is worth noting that the CHANGES_AND_HINTS.TXT that comes with 14 will have the full lists of added and removed packages. For people testing -current, they should really know what they are doing (either using slackpkg correctly or paying very careful attention to the changelog).
 
2 members found this post helpful.
Old 07-15-2012, 07:01 PM   #99
fogpipe
Member
 
Registered: Mar 2011
Distribution: Slackware 64 -current multilib
Posts: 360

Rep: Reputation: 95
Quote:
Originally Posted by ruario View Post
For people testing -current, they should really know what they are doing

While i cant speak for others, that qualification would certainly leave me out.
 
Old 07-16-2012, 03:58 AM   #100
mats_b_tegner
Member
 
Registered: Nov 2009
Location: Gothenburg, Sweden
Distribution: Slackware64
Posts: 145

Rep: Reputation: 47
When I rebooted my -current system today after upgrading to the latest mkinitrd-package and created a new initrd I get a kernel panic:
/bin/ash: error while loading shared libraries: /lib64/libc.so.6 unexpected PLT reloc type 0x25

I tried the following, but the kernel still panics:
Boot from SlackDVD
mkdir /mmt/slack
mount /dev/sda4 /mnt/slack
chroot /mnt/slack
lilo -t -v
mkinitrd -c -k 3.2.23 -m ext4 -f ext4 -r /dev/sda4
lilo

Is there a way to fix this without reinstalling from DVD?

Mats

Edit: I installed the huge kernel and now I can boot the system. I guess the problem lies somewhere with the latest mkinitrd-package.

Last edited by mats_b_tegner; 07-16-2012 at 05:27 AM.
 
Old 07-16-2012, 07:56 AM   #101
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado
Distribution: Slackware
Posts: 421

Rep: Reputation: 58
Confirmed generic kernel panic on reboot after install of latest mkinitrd update. After update, executed mkinitrd_command_generator.sh, executed lilo, reboot to kernel panic with generic kernel. Running on huge kernel for now.
 
1 members found this post helpful.
Old 07-16-2012, 08:08 AM   #102
inph
LQ Newbie
 
Registered: Jul 2012
Posts: 9

Rep: Reputation: Disabled
udev-175-i486-1 e100 firmware loading problems

After updating a machine to -current (32-bit) I'm encountering a problem with udev 175 not loading firmware for an e100 card on boot.

uname -a: Linux 3.2.23-smp #2 SMP Thu Jul 12 21:12:14 CDT 2012 i686 Intel(R) Xeon(TM) CPU 2.40GHz GenuineIntel GNU/Linux

The firmware resides in /lib/firmware/e100
Code:
# ls -la /lib/firmware/e100
-rw-r--r--  1 root root  539 Jun 22 19:58 d101m_ucode.bin
-rw-r--r--  1 root root  539 Jun 22 19:58 d101s_ucode.bin
-rw-r--r--  1 root root  539 Jun 22 19:58 d102e_ucode.bin
Typically after boot the interface will remain down.

Repeatedly trying to bring the interface up will eventually load the firmware. This can take between 2 and 10+ commands one after another (/etc/rc.d./rc.inet1 eth0_start or ifconfig eth0 up).

Immediately after boot: dmesg && ifconfig -a
Code:
[    7.067601] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[    7.067741] e100: Copyright(c) 1999-2006 Intel Corporation
[    7.067979] e100 0000:01:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    7.157845] e100 0000:01:01.0: PME# disabled
[    7.158159] e100 0000:01:01.0: eth0: addr 0xfe7fe000, irq 17, MAC addr 00:e0:81:28:f1:3c
[   13.599574] udevd[1601]: starting version 175
[   14.694232] firmware 0000:01:01.0: firmware_loading_store: unexpected value (0)
[   14.694382] e100 0000:01:01.0: eth0: Failed to load firmware "e100/d102e_ucode.bin": -2

# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:E0:81:28:F1:3C
          inet addr:IPADDR0  Bcast:BROADCAST0  Mask:255.255.255.0
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

eth1      Link encap:Ethernet  HWaddr 00:E0:81:28:F1:3D
          inet addr:10.1.1.1  Bcast:10.1.1.255  Mask:255.255.255.0
          inet6 addr: IPADDR6-0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:529 errors:0 dropped:0 overruns:0 frame:0
          TX packets:494 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:40035 (39.0 Kb)  TX bytes:98977 (96.6 Kb)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Jul 16 11:24:26 udevd[1628]: '/sbin/modprobe -bv acpi:PNP0B00:' [1728] terminated by signal 6 (Aborted)
Jul 16 11:24:26 udevd[1613]: '/sbin/modprobe -bv acpi:PNP0B00:' [1754] terminated by signal 6 (Aborted)
Jul 16 11:24:27 kernel: [   14.694232] firmware 0000:01:01.0: firmware_loading_store: unexpected value (0)
Jul 16 11:24:27 kernel: [   14.694382] e100 0000:01:01.0: eth0: Failed to load firmware "e100/d102e_ucode.bin": -2
Jul 16 11:24:27 udevd[1601]: failed to create queue file: No such file or directory
Jul 16 11:24:30 udevd[1601]: failed to create queue file: No such file or directory
Jul 16 11:24:30 udevd[1344]: failed to create queue file: No such file or directory

Manually forcing the firmware to load (worked on the second try this time):
Code:
# ifconfig eth0 up
SIOCSIFFLAGS: No such file or directory
# ifconfig eth0 up
# ifconfig eth0 up
# /etc/rc.d/rc.inet1 eth0_start
#

[   50.980990] firmware 0000:01:01.0: firmware_loading_store: vmap() failed
[   50.981815] e100 0000:01:01.0: eth0: Failed to load firmware "e100/d102e_ucode.bin": -2

[   51.666329] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   51.667302] e100 0000:01:01.0: eth0: NIC Link is Up 100 Mbps Full Duplex
[   51.667717] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   62.098009] eth0: no IPv6 routers present

Jul 16 11:25:03 kernel: [   50.980990] firmware 0000:01:01.0: firmware_loading_store: vmap() failed
Jul 16 11:25:03 kernel: [   50.981815] e100 0000:01:01.0: eth0: Failed to load firmware "e100/d102e_ucode.bin": -2
This is currently with the stock vmlinuz-huge-smp-3.2.23-smp kernel from -current.
I also tested booting with vmlinuz-huge-smp-3.2.21-smp with udev-175 and encountered the same problem.

Both kernels work fine booting with udev-165 (another partition on same machine running -current from before 13th upgrades.)

The machine is a headless box at a remote location, access is currently via an e1000 which is not affected since it doesn't require firmware.

more dmesg and logs: http://pastie.org/4263341


Running # udevadm monitor --property
During both a failed firmware load and a successful firmware load one after another:

udevadm monitor log: http://pastie.org/4263584


Running: udevadm control --log-priority debug
(Usually) results in the firmware loading immediately after on the next /etc/rc.d/rc.inet1 eth0_start command.

So testing: /etc/udev/udev.conf:udev_log=debug
Did not change the firmware failing to load but produced the following log (trimmed to where e100 starts loading.)

udev_log=debug: http://pastie.org/4263345


Module unloading and reloading:
rmmod e100 && modprobe e100 && ifconfig eth0 up

Produced the same results, often failing and after repeating the same command eventually the firmware would load. dmesg output showed the module unloading and loading with the intel banner: e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI.

Code:
# rmmod e100 && modprobe e100 && /etc/rc.d/rc.inet1 eth0_start
SIOCSIFFLAGS: No such file or directory
# rmmod e100 && modprobe e100 && /etc/rc.d/rc.inet1 eth0_start
SIOCSIFFLAGS: No such file or directory
# rmmod e100 && modprobe e100 && /etc/rc.d/rc.inet1 eth0_start
SIOCSIFFLAGS: No such file or directory
# rmmod e100 && modprobe e100 && /etc/rc.d/rc.inet1 eth0_start
SIOCSIFFLAGS: No such file or directory
# rmmod e100 && modprobe e100 && /etc/rc.d/rc.inet1 eth0_start
# 

[10989.592193] libfcoe_device_notification: NETDEV_UNREGISTER eth0
[10990.603073] e100 0000:01:01.0: PCI INT A disabled
[10990.609956] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[10990.609968] e100: Copyright(c) 1999-2006 Intel Corporation
[10990.610510] e100 0000:01:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[10990.705021] e100 0000:01:01.0: PME# disabled
[10990.706091] e100 0000:01:01.0: eth0: addr 0xfe7fe000, irq 17, MAC addr 00:e0:81:28:f1:3c
[10990.793867] firmware 0000:01:01.0: firmware_loading_store: vmap() failed
[10990.794803] e100 0000:01:01.0: eth0: Failed to load firmware "e100/d102e_ucode.bin": -2
[11015.116821] libfcoe_device_notification: NETDEV_UNREGISTER eth0
[11015.131088] e100 0000:01:01.0: PCI INT A disabled
[11015.137846] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[11015.137853] e100: Copyright(c) 1999-2006 Intel Corporation
[11015.137945] e100 0000:01:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[11015.237033] e100 0000:01:01.0: PME# disabled
[11015.237363] e100 0000:01:01.0: eth0: addr 0xfe7fe000, irq 17, MAC addr 00:e0:81:28:f1:3c
[11015.324970] firmware 0000:01:01.0: firmware_loading_store: unexpected value (0)
[11015.325570] e100 0000:01:01.0: eth0: Failed to load firmware "e100/d102e_ucode.bin": -2
[11016.722352] libfcoe_device_notification: NETDEV_UNREGISTER eth0
[11016.734093] e100 0000:01:01.0: PCI INT A disabled
[11016.740301] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[11016.740310] e100: Copyright(c) 1999-2006 Intel Corporation
[11016.740465] e100 0000:01:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[11016.834030] e100 0000:01:01.0: PME# disabled
[11016.834476] e100 0000:01:01.0: eth0: addr 0xfe7fe000, irq 17, MAC addr 00:e0:81:28:f1:3c
[11016.914961] firmware 0000:01:01.0: firmware_loading_store: vmap() failed
[11016.915220] e100 0000:01:01.0: eth0: Failed to load firmware "e100/d102e_ucode.bin": -2
[11018.177082] libfcoe_device_notification: NETDEV_UNREGISTER eth0
[11018.190100] e100 0000:01:01.0: PCI INT A disabled
[11018.196333] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[11018.196345] e100: Copyright(c) 1999-2006 Intel Corporation
[11018.196519] e100 0000:01:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[11018.291028] e100 0000:01:01.0: PME# disabled
[11018.291491] e100 0000:01:01.0: eth0: addr 0xfe7fe000, irq 17, MAC addr 00:e0:81:28:f1:3c
[11018.378908] firmware 0000:01:01.0: firmware_loading_store: unexpected value (0)
[11018.379872] e100 0000:01:01.0: eth0: Failed to load firmware "e100/d102e_ucode.bin": -2
[11019.429697] libfcoe_device_notification: NETDEV_UNREGISTER eth0
[11019.443091] e100 0000:01:01.0: PCI INT A disabled
[11019.449377] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[11019.449389] e100: Copyright(c) 1999-2006 Intel Corporation
[11019.449567] e100 0000:01:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[11019.545023] e100 0000:01:01.0: PME# disabled
[11019.545440] e100 0000:01:01.0: eth0: addr 0xfe7fe000, irq 17, MAC addr 00:e0:81:28:f1:3c
[11019.637308] ADDRCONF(NETDEV_UP): eth0: link is not ready
[11019.638298] e100 0000:01:01.0: eth0: NIC Link is Up 100 Mbps Full Duplex
[11019.639188] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[11029.778073] eth0: no IPv6 routers present


Jul 16 17:18:52 kernel: [10989.592193] libfcoe_device_notification: NETDEV_UNREGISTER eth0
Jul 16 17:18:52 udevd[1596]: failed to create queue file: No such file or directory
Jul 16 17:18:53 udevd[1596]: failed to create queue file: No such file or directory
Jul 16 17:18:54 kernel: [10990.793867] firmware 0000:01:01.0: firmware_loading_store: vmap() failed
Jul 16 17:18:54 kernel: [10990.794803] e100 0000:01:01.0: eth0: Failed to load firmware "e100/d102e_ucode.bin": -2
Jul 16 17:19:18 kernel: [11015.116821] libfcoe_device_notification: NETDEV_UNREGISTER eth0
Jul 16 17:19:18 udevd[1596]: failed to create queue file: No such file or directory
Jul 16 17:19:18 udevd[1346]: failed to create queue file: No such file or directory
Jul 16 17:19:18 kernel: [11015.324970] firmware 0000:01:01.0: firmware_loading_store: unexpected value (0)
Jul 16 17:19:18 kernel: [11015.325570] e100 0000:01:01.0: eth0: Failed to load firmware "e100/d102e_ucode.bin": -2
Jul 16 17:19:20 kernel: [11016.722352] libfcoe_device_notification: NETDEV_UNREGISTER eth0
Jul 16 17:19:20 udevd[1596]: failed to create queue file: No such file or directory
Jul 16 17:19:20 kernel: [11016.914961] firmware 0000:01:01.0: firmware_loading_store: vmap() failed
Jul 16 17:19:20 kernel: [11016.915220] e100 0000:01:01.0: eth0: Failed to load firmware "e100/d102e_ucode.bin": -2
Jul 16 17:19:21 kernel: [11018.177082] libfcoe_device_notification: NETDEV_UNREGISTER eth0
Jul 16 17:19:21 kernel: [11018.378908] firmware 0000:01:01.0: firmware_loading_store: unexpected value (0)
Jul 16 17:19:21 kernel: [11018.379872] e100 0000:01:01.0: eth0: Failed to load firmware "e100/d102e_ucode.bin": -2
Jul 16 17:19:21 udevd[1596]: failed to create queue file: No such file or directory
Jul 16 17:19:22 kernel: [11019.429697] libfcoe_device_notification: NETDEV_UNREGISTER eth0
Jul 16 17:19:22 udevd[1346]: failed to create queue file: No such file or directory
Jul 16 17:19:23 udevd[1596]: failed to create queue file: No such file or directory
Edit: added rmmod/modeprobe/rc1.inet start outputs

I've looked at the changelog for udev (http://git.kernel.org/?p=linux/hotpl...AD;f=ChangeLog) between 165 and 175 and can't see anything obvious related to firmware loading that changed, although there might be some sort of timeout issue.

Any advice or ideas on where to go and what to try next?

Edit: After 15 reboots where the firmware failed to load, two subsequent in a row reboots the firmware has been loaded at boot time with udev-175. Further reboots is back to failing to load.

output from: modinfo e100
This does not change on either failure or success of loading the firmware.

Code:
# modinfo e100
filename:       /lib/modules/3.2.23-smp/kernel/drivers/net/ethernet/intel/e100.ko
firmware:       e100/d102e_ucode.bin
firmware:       e100/d101s_ucode.bin
firmware:       e100/d101m_ucode.bin
version:        3.5.24-k2-NAPI
license:        GPL
author:         Copyright(c) 1999-2006 Intel Corporation
description:    Intel(R) PRO/100 Network Driver
srcversion:     3CF569461A087DBBBD0E2BD
alias:          pci:v00008086d000027DCsv*sd*bc02sc00i*
alias:          pci:v00008086d0000245Dsv*sd*bc02sc00i*
alias:          pci:v00008086d00002459sv*sd*bc02sc00i*
alias:          pci:v00008086d00002449sv*sd*bc02sc00i*
alias:          pci:v00008086d00001229sv*sd*bc02sc00i*
alias:          pci:v00008086d00001209sv*sd*bc02sc00i*
alias:          pci:v00008086d000010FEsv*sd*bc02sc00i*
alias:          pci:v00008086d00001095sv*sd*bc02sc00i*
alias:          pci:v00008086d00001094sv*sd*bc02sc00i*
alias:          pci:v00008086d00001093sv*sd*bc02sc00i*
alias:          pci:v00008086d00001092sv*sd*bc02sc00i*
alias:          pci:v00008086d00001091sv*sd*bc02sc00i*
alias:          pci:v00008086d0000106Bsv*sd*bc02sc00i*
alias:          pci:v00008086d0000106Asv*sd*bc02sc00i*
alias:          pci:v00008086d00001069sv*sd*bc02sc00i*
alias:          pci:v00008086d00001068sv*sd*bc02sc00i*
alias:          pci:v00008086d00001067sv*sd*bc02sc00i*
alias:          pci:v00008086d00001066sv*sd*bc02sc00i*
alias:          pci:v00008086d00001065sv*sd*bc02sc00i*
alias:          pci:v00008086d00001064sv*sd*bc02sc00i*
alias:          pci:v00008086d00001059sv*sd*bc02sc00i*
alias:          pci:v00008086d00001057sv*sd*bc02sc00i*
alias:          pci:v00008086d00001056sv*sd*bc02sc00i*
alias:          pci:v00008086d00001055sv*sd*bc02sc00i*
alias:          pci:v00008086d00001054sv*sd*bc02sc00i*
alias:          pci:v00008086d00001053sv*sd*bc02sc00i*
alias:          pci:v00008086d00001052sv*sd*bc02sc00i*
alias:          pci:v00008086d00001051sv*sd*bc02sc00i*
alias:          pci:v00008086d00001050sv*sd*bc02sc00i*
alias:          pci:v00008086d0000103Esv*sd*bc02sc00i*
alias:          pci:v00008086d0000103Dsv*sd*bc02sc00i*
alias:          pci:v00008086d0000103Csv*sd*bc02sc00i*
alias:          pci:v00008086d0000103Bsv*sd*bc02sc00i*
alias:          pci:v00008086d0000103Asv*sd*bc02sc00i*
alias:          pci:v00008086d00001039sv*sd*bc02sc00i*
alias:          pci:v00008086d00001038sv*sd*bc02sc00i*
alias:          pci:v00008086d00001034sv*sd*bc02sc00i*
alias:          pci:v00008086d00001033sv*sd*bc02sc00i*
alias:          pci:v00008086d00001032sv*sd*bc02sc00i*
alias:          pci:v00008086d00001031sv*sd*bc02sc00i*
alias:          pci:v00008086d00001030sv*sd*bc02sc00i*
alias:          pci:v00008086d00001029sv*sd*bc02sc00i*
depends:        mii
intree:         Y
vermagic:       3.2.23-smp SMP mod_unload PENTIUMIII
parm:           debug:Debug level (0=none,...,16=all) (int)
parm:           eeprom_bad_csum_allow:Allow bad eeprom checksums (int)
parm:           use_io:Force use of i/o access mode (int)

Last edited by inph; 07-16-2012 at 12:40 PM.
 
Old 07-16-2012, 08:57 AM   #103
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,651
Blog Entries: 2

Rep: Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095
Just upgraded my main machine (64 bit) after all errors on my laptop were worked out. Upgrade wnt fine and I have no problems to boot with the generic kernel. I used
Code:
mkinitrd -c -k 3.2.23 -f ext4 -r /dev/sda2 -u -m ext4
to create the initrd.
 
1 members found this post helpful.
Old 07-16-2012, 09:56 AM   #104
mats_b_tegner
Member
 
Registered: Nov 2009
Location: Gothenburg, Sweden
Distribution: Slackware64
Posts: 145

Rep: Reputation: 47
Quote:
Originally Posted by TobiSGD View Post
Just upgraded my main machine (64 bit) after all errors on my laptop were worked out. Upgrade wnt fine and I have no problems to boot with the generic kernel. I used
Code:
mkinitrd -c -k 3.2.23 -f ext4 -r /dev/sda2 -u -m ext4
to create the initrd.
I used the same mkinitrd line and I get a kernel panic.
 
Old 07-16-2012, 11:45 AM   #105
michelino
LQ Newbie
 
Registered: Dec 2006
Posts: 24

Rep: Reputation: 0
Same problem here:
/bin/ash: error while loading shared libraries: /lib64/libc.so.6 unexpected PLT reloc type 0x25

I did (using slack 13.37 "live dvd"):

mkdir fr
mount dev/sda1 fr/
mount -o bind proc/ fr/proc
mount -o bind sys/ fr/sys
mount -o bind dev/ fr /dev

chroot fr/

cd /boot

mkinitrd -c -k 3.2.23 -m ext4

lilo -v

.....but still "panic"

Edit: I'm in multilib system, but I've tried to revert to "clean" system, same problem

Last edited by michelino; 07-16-2012 at 11:46 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Microsoft forms open source subsidiary on Friday the 13th LXer Syndicated Linux News 0 04-13-2012 07:50 PM
LXer: Linux Gets Gooey on Friday the 13th LXer Syndicated Linux News 0 02-13-2009 11:10 PM
LXer: One of those magic times: On Friday the 13th! LXer Syndicated Linux News 1 02-07-2009 10:43 AM
LQ Security Report - February 13th 2005 Capt_Caveman Linux - Security 4 02-13-2005 10:51 PM
LQ security report - Feb 13th 2004 unSpawn Linux - Security 5 02-13-2004 12:36 PM


All times are GMT -5. The time now is 10:27 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration