LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
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 08-16-2012, 11:16 AM   #16
salparadise
Senior Member
 
Registered: Nov 2002
Location: Birmingham UK
Distribution: Various
Posts: 1,736

Rep: Reputation: 146Reputation: 146

With one exception all is working nicely here.

Network Manager reports "no network interface found". When right clicked it reports it is not started and does not respond to checking the "Start Network Manager" box. When I installed RC1, I had the same with no network connection at all. This time the connection is present.
 
Old 08-16-2012, 11:38 AM   #17
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,371

Rep: Reputation: 2749Reputation: 2749Reputation: 2749Reputation: 2749Reputation: 2749Reputation: 2749Reputation: 2749Reputation: 2749Reputation: 2749Reputation: 2749Reputation: 2749
Is /etc/rc.d/rc.networkmanager executable so that the NetworkManager daemon is started at boot?
 
1 members found this post helpful.
Old 08-16-2012, 12:38 PM   #18
salparadise
Senior Member
 
Registered: Nov 2002
Location: Birmingham UK
Distribution: Various
Posts: 1,736

Rep: Reputation: 146Reputation: 146
Is /etc/rc.d/rc.networkmanager executable so that the NetworkManager daemon is started at boot?

Sorted,thanks. You're a steely eyed muscle man.
;-)
 
Old 08-16-2012, 12:41 PM   #19
Martinus2u
Member
 
Registered: Apr 2010
Distribution: Slackware
Posts: 497

Rep: Reputation: 119Reputation: 119
let's hope the release gets a decent maturation period since there have been a lot of changes recently...
 
Old 08-16-2012, 02:20 PM   #20
hitest
Guru
 
Registered: Mar 2004
Location: Canada
Distribution: Void, Debian, Slackware
Posts: 7,342

Rep: Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746
Quote:
Originally Posted by Martinus2u View Post
let's hope the release gets a decent maturation period since there have been a lot of changes recently...
As always 14.0 will be released when it is ready.
I am content to wait while Mr. Volkerding finalizes this release.
 
1 members found this post helpful.
Old 08-16-2012, 04:55 PM   #21
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,557

Rep: Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761
I noticed the following on the Arch Wiki Syslinux page, under the MBR section.

Quote:
Note: An alternate MBR doesn't work properly in Syslinux 4.05 - it always invokes first partition. This bug was fixed in this commit: https://git.kernel.org/?p=boot/sysli...db29040b096e45.
I see that -current has version 4.05. Is the fix present (I must admit I have not actually tested yet)? If not, too late to consider taking in the fix?

Edit: I looked at the source in -current and see that the patch hasn't been applied. This is all that is needed to fix the issue:

Code:
--- ./mbr/altmbr.S
+++ ./mbr/altmbr.S
@@ -204,7 +204,7 @@ scan_partition_table:
 5:
        decb    (partition)
        jz      boot
-       addw    $16, %bx
+       addw    $16, %si
        loopw   5b
 
        popw    %cx                     /* %cx <- 4    */

Last edited by ruario; 08-17-2012 at 01:50 AM.
 
1 members found this post helpful.
Old 08-16-2012, 06:09 PM   #22
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,845

Rep: Reputation: 452Reputation: 452Reputation: 452Reputation: 452Reputation: 452
Ok, got the update done and all is well. Then again, I'm only a few minutes in, but a successful boot is a great start!
 
Old 08-16-2012, 08:14 PM   #23
zbreaker
Member
 
Registered: Dec 2008
Location: New York
Distribution: Slack -current, siduction
Posts: 253

Rep: Reputation: 29
Quote:
Originally Posted by mlangdn View Post
Ok, got the update done and all is well. Then again, I'm only a few minutes in, but a successful boot is a great start!
+1

So far....so good!

Many thanks to Pat and the team
 
Old 08-16-2012, 09:45 PM   #24
kikinovak
MLED Founder
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453

Rep: Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154
A small error in 13.37, don't know if it's fixed yet, but here it is.

When installing from a USB disk on a PC without optical drive, one has to mount the disk at some point and choose "Install from a pre-mounted directory". Then, at some later point, the installer declares that "FAT partitions have been detected", and should they be added to LILO? Choosing "no" has no consequence here, as the according "Windows" stanza gets added to LILO anyway (as default). Of course it's easy to get rid of it after rebooting, but the first time this happened, I didn't pay attention and was slightly puzzled by the ensuing "Kernel panic" after rebooting.
 
Old 08-16-2012, 10:19 PM   #25
SqdnGuns
Senior Member
 
Registered: Aug 2005
Location: Pensacola, FL
Distribution: Slackware64® Current & Arch
Posts: 1,092

Rep: Reputation: 174Reputation: 174
Slackware 14 RC 2 Announced

Quote:
Originally Posted by kikinovak View Post
A small error in 13.37
Huh?
 
Old 08-17-2012, 12:24 AM   #26
salparadise
Senior Member
 
Registered: Nov 2002
Location: Birmingham UK
Distribution: Various
Posts: 1,736

Rep: Reputation: 146Reputation: 146
Much was made of the Gimp 2.8 and how it has "single window mode".
Gimp 2.8 is installed with Slackware 14 but has multiple window mode - can this be changed, or did "single window mode" get dropped by the Gimp Devs?
 
Old 08-17-2012, 12:56 AM   #27
escaflown
Member
 
Registered: Apr 2009
Location: Canada
Distribution: Slackware
Posts: 239

Rep: Reputation: 31
Quote:
Originally Posted by salparadise View Post
Much was made of the Gimp 2.8 and how it has "single window mode".
Gimp 2.8 is installed with Slackware 14 but has multiple window mode - can this be changed, or did "single window mode" get dropped by the Gimp Devs?
All you need to do is "Widows->Single-window mode"
 
Old 08-17-2012, 01:03 AM   #28
salparadise
Senior Member
 
Registered: Nov 2002
Location: Birmingham UK
Distribution: Various
Posts: 1,736

Rep: Reputation: 146Reputation: 146
Thanks.
I'd like to say "that'll teach me to post without exploring the menus", but it probably won't.
 
Old 08-17-2012, 05:00 AM   #29
CTM
Member
 
Registered: Apr 2004
Distribution: Slackware
Posts: 308

Rep: Reputation: 287Reputation: 287Reputation: 287
Code:
ap/mpg123-1.14.4-x86_64-1.txz:  Upgraded.
Thanks for this, much appreciated
 
Old 08-17-2012, 05:34 AM   #30
hotchili
Member
 
Registered: Sep 2009
Location: Germany
Distribution: slackware64-current
Posts: 89

Rep: Reputation: 32
Hello

Quote:
Originally Posted by zakame View Post
I think this was reported before, but I get a

Code:
udevd[XXXX]: seq 1251 '/devices/pci0000:00/0000:00:04.0/0000:01:00.0' killed
udevd[XXXX]: worker [XXXX] terminated by signal 9 (Killed)
upon bootup with the stock generic-3.2.27 kernel, on my Asus 1215B. This does not appear in my custom 3.5.1 kernel, nor in stock generic-3.2.27 in my ThinkPad T61.

The device probed above seems to be a

Code:
00:04.0 PCI bridge: Advanced Micro Devices [AMD] Family 14h Processor Root Port
according to lspci.
I have the same netbook, so I had the same problem.

After some google searching I found that the delay/error at boot is caused
by a change in udev. They changed the way it loads drivers with firmware,
if udev detects the driver is not updated for that, it pauses for a 30seconds delay.

This can only be fixed by the author of the kernel module which is causing it.
(Thats why your 3.5 kernel is fine, probably its fixed there)

A workaround for that problem is to blacklist the offending module in /etc/modprobe.d/blacklist.conf
(in my case it was brcmsmac, the wifi driver) and later load it in rc.local (modprobe brcmsmac)

Greetings
 
4 members found this post helpful.
  


Reply



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: Slackware 14.0 release candidate 1 announced. LXer Syndicated Linux News 0 08-11-2012 08:45 PM
Gnome 4 announced! DavidMcCann General 0 04-01-2012 11:14 AM
dreamlinux v5alpha has been announced, but... verdaz Dreamlinux 5 01-07-2012 01:50 PM
LXer: Slackware 13.1 Beta announced. LXer Syndicated Linux News 3 05-11-2010 02:51 PM
BhutanLinux announced! snecklifter Linux - News 8 04-10-2005 12:38 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:35 PM.

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
Open Source Consulting | Domain Registration