slackware 13.0 hugesmb / hald / network issue????

mrmnemo · 09-06-2009, 04:10 PM

I actually have issues that I think are separate.

1. I am getting dbus errors when inserting iso9660 cd-r that i have burned which causes crash of KDE and faulting out to x and locking. in kde 4 plasma crashes randomly ( cant find what the trigger is yet).

2. Wireless is SLOOOOOWWWWW. As a test i ran "iwconfig rate 54M [fixed]" to see if that was the issue due to the bit rate registering as 1 mb/s after boot. It made no diff at all. I am using wicd at the moment however I had the same issue when I set up the wireless via wpa_supplicant.
##info wireless driver ralink

Assumptions:

I am thinking my problems might be related to something with the kernel but i am kinda new to alot of this. however, from term i have been seeing lots of kernel faults while doing anything scsi related. which since i am using a wireless usb stick and having issues with my cd roms and mem sticks that would be understandable.

If i am wrong let me know. I had no problems with 12.2 AT ALL. I am wondering whats so special about 13 other than i didnt have to run /usr/bin/x11r6... to get x coinfigured seems they wanted it to be automatic.

HELP!!

mrmnemo · 09-06-2009, 06:10 PM

am i the only one with these problems?

gegechris99 · 09-07-2009, 06:52 AM

Hello,

Problem 1: I assume that you have tried the CD on another system to make sure it's not broken.

Does your user belong to group "cdrom"? If you're not sure, please post the result of this command:

Code:

cat /etc/group | grep username

Replace username with your actual user id

Problem 2: It's difficult to appreciate speed on internet connection. It could be a temporary disturbance on the part of your ISP. Did you keep 12.2 in another partition? If so, do you "see" a tangible difference of internet speed when you use 12.2 in comparison to 13.0?

mrmnemo · 09-07-2009, 02:48 PM

Quote:

bash-3.1# cat /etc/group | grep mnemo
floppy:x:11:root,mnemo
audio:x:17:root,mnemo
video:x:18:root,mnemo
cdrom:x:19:root,mnemo
plugdev:x:83:root,mnemo
power:x:84:root,mnemo
netdev:x:86:root,mnemo

wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate:108 Mb/s
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

wmaster0 no wireless extensions.

wlan1 IEEE 802.11bg ESSID:"teasley"
Mode:Managed Frequency:2.462 GHz Access Point: 00:12:0E:5A:CD:D2
Bit Rate=1 Mb/s Tx-Power=20 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:9F52-BAB8-8E4F-4B4D-5227-C1E5-E1DD-4FD0 [2] Security mode:open
Power Management:off
Link Quality=53/100 Signal level:-64 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Some sys log entries that stuck out :

Quote:

2009-09-07 02:59:05 mnemo kernel phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x0428 with error -19.

2009-09-07 02:59:05 mnemo kernel phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x0428 with error -19.
2009-09-07 04:13:58 CPU Hyper-Threading is disabled
2009-09-07 04:13:58 Intel machine check architecture supported.
2009-09-07 04:13:58 Intel machine check reporting enabled on CPU#0.
2009-09-07 04:13:58 CPU0 Intel P4/Xeon Extended MCE MSRs (12) available
2009-09-07 04:13:58 Checking 'hlt' instruction... OK.
2009-09-07 04:13:58 SMP alternatives switching to UP code
2009-09-07 04:13:58 Freeing SMP alternatives: 38k freed
2009-09-07 04:13:58 ACPI Core revision 20081204
2009-09-07 04:13:58 ACPI setting ELCR to 0200 (from 0820)
2009-09-07 04:13:58 weird, boot CPU (#0) not listed by the BIOS.
2009-09-07 04:13:58 SMP motherboard not detected.
2009-09-07 04:13:58 Local APIC not detected. Using dummy APIC emulation.
2009-09-07 04:13:58 SMP disabled
2009-09-07 04:13:58 Brought up 1 CPUs
2009-09-07 04:13:58 Total of 1 processors activated (3386.29 BogoMIPS).

----more lines-----and then-------

2009-09-07 04:13:58 usb 1-1 New USB device found, idVendor=07d1, idProduct=3a08
2009-09-07 04:13:58 usb 1-1 New USB device strings: Mfr=1, Product=2, SerialNumber=3
2009-09-07 04:13:58 usb 1-1 Product: USB WLAN Device
2009-09-07 04:13:58 usb 1-1 Manufacturer: Atheros Communications Inc
2009-09-07 04:13:58 usb 1-1 SerialNumber: 1.0
2009-09-07 04:13:58 usb 1-1 configuration #1 chosen from 1 choice
2009-09-07 04:13:58 usb 1-2 new high speed USB device using ehci_hcd and address 3
2009-09-07 04:13:58 usb 1-2 New USB device found, idVendor=148f, idProduct=2570
2009-09-07 04:13:58 usb 1-2 New USB device strings: Mfr=1, Product=2, SerialNumber=0
2009-09-07 04:13:58 usb 1-2 Product: 802.11g WLAN + Pen Drive
2009-09-07 04:13:58 usb 1-2 Manufacturer: Ralink
2009-09-07 04:13:58 usb 1-2 configuration #1 chosen from 1 choice

i am not sure what eelse to put up for you. thanks again for the help.

gegechris99 · 09-07-2009, 04:35 PM

If you think the kernel may be the source of your errors, you might want to try the generic SMP kernel instead of the huge one.

As written in file CHANGES_AND_HINTS.TXT:

Quote:

Use one of the provided generic kernels for daily use. Do not report
bugs until/unless you have reproduced them using one of the stock
generic kernels. You will need to create an initrd in order to boot
the generic kernels - see /boot/README.initrd for instructions.
The huge kernels are primarily intended as "installer" and "emergency"
kernels in case you forget to make an initrd. For most systems, you
should use the generic SMP kernel if it will run, even if your system is
not SMP-capable. Some newer hardware needs the local APIC enabled in the
SMP kernel, and theoretically there should not be a performance penalty
with using the SMP-capable kernel on a uniprocessor machine, as the SMP
kernel tests for this and makes necessary adjustments. Furthermore, the
kernel sources shipped with Slackware are configured for SMP usage, so you
won't have to modify those to build external modules (such as NVidia or
ATI proprietary drivers) if you use the SMP kernel.

mrmnemo · 09-07-2009, 08:20 PM

Quote:

Originally Posted by gegechris99

If you think the kernel may be the source of your errors, you might want to try the generic SMP kernel instead of the huge one.

As written in file CHANGES_AND_HINTS.TXT:

well i spoke a lil fast on that subject. after looking into things i had my hardware wrong. however, this install is using the default kernel (hugesmb.s) --as i did not enter anything different in the install. also, unlike in 12.2 13 tried to setup the specs on my video card on its own using HALD. i noticed that the rev code and mdl ofg my video card are not exactly the same as the actual card is. also, i think the card was id'ed as having 128mb rather than the 32mb it really has. i tried to run /usr/X11R6/bin/xorg/config like in 1`2.2 but couldnt get it to run as it says not .config file exist. could this be PART of my problem?

gegechris99 · 09-08-2009, 03:03 AM

I think you can try to set up Xorg to select your own driver.

Refer to file Slackware-HOWTO:

Quote:

6.2 Configuring the X Window System

Configuring X can be a complex task. The reason for this is the vast
numbers of video cards available for the PC architecture, most of which
use different programming interfaces. Luckily, X has come a long way
since the early days of X386, where monitor modelines had to be tediously
calculated. With most hardware, X can now be run with NO configuration
file or additional driver! But you still might want to make a
configuration file if you'll be using a third party video driver (the
installer for that may offer to make it for you), or if you just want to
have greater control over the details of the X configuration.

To try X without a configuration file, just type "startx" at a command
line. If you're satisfied with the result, then you're done. If you
would like X to start automatically at boot, see the /etc/inittab file
once you've tested "startx" to be sure that X is working.

If this doesn't work with your card, or if you'd like to take advantage of
the high-performance features of your video card such as hardware
acceleration or 3-D hardware rendering, then you'll need to reconfigure X.

To configure X, you'll need to make an /etc/X11/xorg.conf file. This file
contains lots of details about your video hardware, mouse, and monitor.
It's a very complex configuration file, but fortunately there are several
programs to help create one for you. We'll mention a few of them here:

Xorg -configure
---------------

Modern versions of X provide a simple way to create an initial xorg.conf
file that often will work without any additional configuration, or, at the
very least, provide a good base from which to customize the file. To run
this command, enter the following in a root terminal:

# Xorg -configure

The X server probes for available hardware and creates an initial
xorg.file located in the /root directory. You can then use this initial
file to test the configuration by entering the following:

# Xorg -config /root/xorg.conf.new

This will load the initial xorg.conf.new file and run the X server. If
you see the default black and gray checkered background with a mouse
cursor appear, then the configuration was successful. To exit the X
server, just press Ctrl+Alt+Backspace simultaneously. Once back at the
command line, you can copy this xorg.conf.new file to /etc/X11/xorg.conf
and begin making any manual edits necessary to customize your setup.

xorgsetup
---------

This is a simple menu driven frontend that's similar in feel to the
Slackware installer. It simply tells the X server to take a look at the
card, and then set up the best initial configuration file it can make
based on the information it gathers. The generated /etc/X11/xorg.conf
file should be a good starting point for most systems (and should work
without modification).

Another alternative is to copy the /etc/X11/xorg.conf file from 12.2 into 13.0 (if you did not do any configuration, there is currently no /etc/X11/xorg.conf file in your 13.0)

mrmnemo · 09-08-2009, 02:29 PM

Update: I just reverted back to 12.2. and so far everything seems to be working fine. with the exception of the dlink card i have being picked up. ndiswrapper is setup with the correct driver and sees the card but it doesnt show as an available interface. but that is another problem. thanks for the help.