Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Mon 15 Sep 2014, 05:34
All times are UTC - 4
 Forum index » Advanced Topics » Cutting edge
Slaxer_Pup 4.12 solid and stable non woof build
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 5 of 32 [470 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, ..., 30, 31, 32 Next
Author Message
davids45


Joined: 26 Nov 2006
Posts: 647
Location: Chatswood, NSW

PostPosted: Tue 21 Apr 2009, 21:25    Post subject: Our Medion 8818s  

G'day Béèm,
I see you've tried the latest smp-capable Pups but still are having no luck with your unmodified Medion 8818. I was going to suggest you try the Slaxer Pup as something different but you beat me to it. Sorry to hear it did not work for you.
On my BIOS-modified 8818, I had not had any problems with any Pups until I tried wow's unnamed and MU's newyear's Pups. I think I have the same problem on my 8818 you report where there is an error during live-CD boot-up and the computer freezes. On my hyper-threading 8383 at home and HT Pentium-4 HP at work, I had these live Pups boot up OK so it may be something else in the dual-core 8818 BIOS setting that is incompatible with these particular Pups.
Here's hoping Woof will be the answer for you and the 8818, in one version or another,
Regards,
David S.
Back to top
View user's profile Send private message 
Béèm


Joined: 21 Nov 2006
Posts: 11782
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win

PostPosted: Wed 22 Apr 2009, 03:11    Post subject:  

Hi davids45,
Glad to hear from my fellow MD8818-er.
An as the saying is: A shared burden is half a burden. Wink

On the smp front, the 420smp is working and I can the two processors.
But the kernel level is too low to see the second sata HDD.

As is with this slaxer 4.12.

I didn't know MU's newyears pup was kinda like wow's unamed, so using the 2.6.28.5 kernel as well?
But giving a problem at boot as well.

So the onlu pup around now id Barry's upup-015 (Intrepid) which supports the second HDD and the kernel being at 2.6.29.rc7
Therefor I was happy to read that Barry did choose the 2.6.29.1 kernel.
However this upup-015 doesn't support the older sfs 3 files, as it is now at sfs 4.
Barry has mentioned this, and I think he is working on the issue.

So to have f.e. OOo in this upup-015, I couldn't use the OOo 3.01 sfs, but with the help of another puppy I made the /opt directory with OOo in it and copied it to upup-015.
This took quite some space of the personal storage, but I can use OOo 3.01 now.
As I have access to my second sata HDD now, I can access my data files on the desktop and don't have to use the laptop for it.

And with the 1GB of ram, puppy's are now very snappy.

As upup-461 (Jaunty) has a lower kernel, it doesn't see the second sata HDD.

So you have in a nutshell my puppy and woof experience.

Cheers, Bernard

_________________
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch
Back to top
View user's profile Send private message 
big_bass

Joined: 13 Aug 2007
Posts: 1747

PostPosted: Wed 22 Apr 2009, 09:43    Post subject:  

Béèm

thanks for posting

if you want to get some help

the best way will be running
this script and attaching the info to this thread
many people will be able to read it
improving your chances

I am working on the USB problem now
but having detailed info helps to solve problems
more quickly

there are a lot of programs that interact
the support may be there but not configured correctly
in the scripts so the first step is to see if the support is there
if it is what is needed to correctly configure it
Code:

#!/bin/sh
#quick info grabbing for testing now all the
#important info is in root with a .gz format
#making it easy for you to upload information
#and attach to a forum post....big_bass
#the files below get placed in root
 
#dmesg.txt.gz
#bootkernel.log.gz
#cpuintfo.txt.gz
#xerrs.log.gz
#Xorg.0.log.gz



dmesg >/root/dmesg.txt&&gzip /root/dmesg.txt
cat /proc/cpuinfo>/root/cpuinfo.txt&&gzip /root/cpuinfo.txt
cp /tmp/bootkernel.log /root&& gzip /root/bootkernel.log
cat /var/log/Xorg.0.log>/root/Xorg.0.log&& gzip /root/Xorg.0.log
cat /tmp/xerrs.log>/root/xerrs.log&& gzip /root/xerrs.log


big_bass
info_get.tar.gz
Description 
gz

 Download 
Filename  info_get.tar.gz 
Filesize  414 Bytes 
Downloaded  402 Time(s) 
Back to top
View user's profile Send private message 
tony

Joined: 14 Jan 2006
Posts: 316
Location: Montreal.ca

PostPosted: Mon 27 Apr 2009, 06:06    Post subject:
Subject description: Repositry
 

Hi big_bass,

Is there a gslapt package that would work with this ?

Regards Tony.
Back to top
View user's profile Send private message 
big_bass

Joined: 13 Aug 2007
Posts: 1747

PostPosted: Mon 27 Apr 2009, 11:00    Post subject:
Subject description: Repositry
 

tony wrote:
Hi big_bass,

Is there a gslapt package that would work with this ?

Regards Tony.


Hey tony

gslap works well with slackware people say .......
but even on the "official" slackware
I don't use it

what I do use on "official" slackware is
src2pkg which is a source to package tool

that gives me much more control of how and what I install
since I do a lot of work on the computer
I cant afford to lose work

and auto installing as fun as it could be is too"risky" for me

now if you set up another machine as a test bed thats fine

*DISCLAIMER*
and on "puppy" if you had good results
using gslapt on version 4.12 puppy and documented
working packages they would also work in slaxer_pup
that said



I personally use pkgtool "official slackware tools" on puppy
the old fashioned way still works for me

I will make a pet package for puppy of pkgtool because if not done
right locks the computer I fixed that problem

I use this myself but didn't want to complicate things at this point
since I was hoping to get feedback on if all the hardware
was getting detected

I have many "tools " for package building that I have been using for a long time so they are well tested
that will get included as pet packages and do work
with the official 4.12 also
so .......


did slaxer_pup detect all your hardware correctly Smile

big_bass

_________________
debian wheezy ,linux mint, slackware I use them all and they all have good points
Mint would be best for general users though
Back to top
View user's profile Send private message 
Béèm


Joined: 21 Nov 2006
Posts: 11782
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win

PostPosted: Mon 27 Apr 2009, 16:54    Post subject:  

Béèm wrote:
But the kernel level is too low to see the second sata HDD.

As is with this slaxer 4.12.

Output of info_get.
(btw the info_get.gz contains info _get, a space too much)
bootkernel log
Code:

und
Serial: 8250/16550 driver4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0c: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
brd: module loaded
loop: module loaded
Compaq SMART2 Driver (v 2.6.0)
HP CISS Driver (v 3.6.20)
Uniform Multi-Platform E-IDE driver
via82cxxx 0000:00:0f.1: VIA vt8251 (rev 00) IDE UDMA133
via82cxxx 0000:00:0f.1: IDE controller (0x1106:0x0571 rev 0x07)
via82cxxx 0000:00:0f.1: IDE port disabled
via82cxxx 0000:00:0f.1: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xe800-0xe807
Probing IDE interface ide0...
hda: HL-DT-STDVD-RAM GSA-H20L, ATAPI CD/DVD-ROM drive
hdb: HL-DT-STDVD-ROM GDR8164B, ATAPI CD/DVD-ROM drive
hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4
hda: UDMA/33 mode selected
hdb: host max PIO5 wanted PIO255(auto-tune) selected PIO4
hdb: UDMA/33 mode selected
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide_generic: please use "probe_mask=0x3f" module parameter for probing all legacy ISA IDE ports
ide_generic: I/O resource 0x1F0-0x1F7 not free.
ide_generic: I/O resource 0x170-0x177 not free.
hda: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache
Uniform CD-ROM driver Revision: 3.20
hdb: ATAPI 48X DVD-ROM drive, 256kB Cache
ide-floppy driver 1.00
Loading iSCSI transport class v2.0-870.
iscsi: registered transport (tcp)
Loading Adaptec I2O RAID: Version 2.4 Build 5go
Detecting Adaptec I2O RAID controllers...
Adaptec aacraid driver 1.1-5[2456]-ms
aic94xx: Adaptec aic94xx SAS/SATA driver version 1.0.3 loaded
scsi: <fdomain> Detection failed (no card)
sym53c416.c: Version 1.0.0-ac
qlogicfas: no cards were found, please specify I/O address and IRQ using iobase= and irq= options<6>QLogic Fibre Channel HBA Driver: 8.02.01-k7
iscsi: registered transport (qla4xxx)
QLogic iSCSI HBA Driver
Emulex LightPulse Fibre Channel SCSI driver 8.2.7
Copyright(c) 2004-2008 Emulex.  All rights reserved.
Failed initialization of WD-7000 SCSI card!
DC390: clustering now enabled by default. If you get problems load
   with "disable_clustering=1" and report to maintainers
megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006)
megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006)
megasas: 00.00.04.01 Thu July 24 11:41:51 PST 2008
GDT-HA: Storage RAID Controller Driver. Version: 3.05
3ware Storage Controller device driver for Linux v1.26.02.002.
3ware 9000 Storage Controller device driver for Linux v2.26.02.011.
nsp32: loading...
ipr: IBM Power RAID SCSI Device Driver version: 2.4.1 (April 24, 2007)
RocketRAID 3xxx/4xxx Controller driver v1.3 (071203)
st: Version 20080504, fixed bufsize 32768, s/g segs 256
Driver 'st' needs updating - please use bus_type methods
Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
sata_via 0000:00:0f.0: version 2.3
sata_via 0000:00:0f.0: PCI INT B -> GSI 21 (level, low) -> IRQ 21
sata_via 0000:00:0f.0: routed to hard irq line 11
scsi2 : sata_via
scsi3 : sata_via
ata1: SATA max UDMA/133 cmd 0xfc00 ctl 0xf800 bmdma 0xec00 irq 21
ata2: SATA max UDMA/133 cmd 0xf400 ctl 0xf000 bmdma 0xec08 irq 21
ata1: SATA link up 1.5 Gbps (SStatus C722FF03 SControl 0)
ata1.00: ATA-7: ST3320820AS, 3.AAC, max UDMA/133
ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata1.00: configured for UDMA/133
ata2: SATA link up 1.5 Gbps (SStatus C722FF03 SControl 0)
scsi 2:0:0:0: Direct-Access     ATA      ST3320820AS      3.AA PQ: 0 ANSI: 5
sd 2:0:0:0: [sda] 625142448 512-byte hardware sectors (320073 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 2:0:0:0: [sda] 625142448 512-byte hardware sectors (320073 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 < sda5 >
sd 2:0:0:0: [sda] Attached SCSI disk
I2O subsystem v1.325
i2o: max drivers = 8
I2O Configuration OSM v1.323
I2O Bus Adapter OSM v1.317
I2O Block Device OSM v1.325
I2O SCSI Peripheral OSM v1.316
I2O ProcFS OSM v1.316
Fusion MPT base driver 3.04.07
Copyright (c) 1999-2008 LSI Corporation
Fusion MPT SPI Host driver 3.04.07
Fusion MPT FC Host driver 3.04.07
Fusion MPT SAS Host driver 3.04.07
ohci1394 0000:07:0c.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[19]  MMIO=[df5fe000-df5fe7ff]  Max Packet=[2048]  IR/IT contexts=[4/8]
usbmon: debugfs is not available
ehci_hcd 0000:00:10.4: PCI INT C -> GSI 22 (level, low) -> IRQ 22
ehci_hcd 0000:00:10.4: EHCI Host Controller
ehci_hcd 0000:00:10.4: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:10.4: debug port 1
ehci_hcd 0000:00:10.4: irq 22, io mem 0xdfffe000
ehci_hcd 0000:00:10.4: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
116x: driver isp116x-hcd, 03 Nov 2005
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
USB Universal Host Controller Interface driver v3.0
uhci_hcd 0000:00:10.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
uhci_hcd 0000:00:10.0: UHCI Host Controller
uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:10.0: irq 20, io base 0x0000e400
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
usb 1-1: new high speed USB device using ehci_hcd and address 2
uhci_hcd 0000:00:10.1: PCI INT C -> GSI 22 (level, low) -> IRQ 22
uhci_hcd 0000:00:10.1: UHCI Host Controller
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:10.1: irq 22, io base 0x0000e000
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
uhci_hcd 0000:00:10.2: PCI INT B -> GSI 21 (level, low) -> IRQ 21
uhci_hcd 0000:00:10.2: UHCI Host Controller
uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:10.2: irq 21, io base 0x0000dc00
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
usb 1-4: new high speed USB device using ehci_hcd and address 3
uhci_hcd 0000:00:10.3: PCI INT D -> GSI 23 (level, low) -> IRQ 23
uhci_hcd 0000:00:10.3: UHCI Host Controller
uhci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:10.3: irq 23, io base 0x0000d800
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
usb 1-4: configuration #1 chosen from 1 choice
usb 1-1.1: new high speed USB device using ehci_hcd and address 4
sl811: driver sl811-hcd, 19 May 2005
Initializing USB Mass Storage driver...
usb 1-1.1: configuration #1 chosen from 1 choice
usb 1-1.2: new high speed USB device using ehci_hcd and address 5
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[0010dc00010c009d]
usb 1-1.2: configuration #1 chosen from 1 choice
usb 1-1.3: new low speed USB device using ehci_hcd and address 6
usb 1-1.3: configuration #1 chosen from 1 choice
scsi4 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
scsi5 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
input: AT Translated Set 2 keyboard as /class/input/input3
raid6: int32x1    722 MB/s
raid6: int32x2    749 MB/s
raid6: int32x4    582 MB/s
raid6: int32x8    520 MB/s
raid6: mmxx1     2356 MB/s
raid6: mmxx2     2785 MB/s
raid6: sse1x1    1671 MB/s
raid6: sse1x2    2131 MB/s
raid6: sse2x1    3162 MB/s
raid6: sse2x2    3810 MB/s
raid6: using algorithm sse2x2 (3810 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
md: multipath personality registered for level -4
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@redhat.com
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
Starting balanced_irq
Using IPI No-Shortcut mode
Freeing unused kernel memory: 392k freed
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
squashfs: version 3.4 (2008/08/26) Phillip Lougher
squashfs: LZMA suppport for slax.org by jro
aufs 20081117
fuse init (API version 7.9)
scsi 4:0:0:0: Direct-Access     EPSON    Stylus Storage   1.00 PQ: 0 ANSI: 2
sd 4:0:0:0: [sdb] Attached SCSI removable disk
usb-storage: device scan complete
scsi 5:0:0:0: Direct-Access     Generic  Flash HS-CF      4.44 PQ: 0 ANSI: 0
sd 5:0:0:0: [sdc] Attached SCSI removable disk
usb-storage: device scan complete
udevd version 124 started
parport_pc 00:0d: reported by Plug and Play ACPI
parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
Linux agpgart interface v0.103
agpgart: Detected VIA P4M890 chipset
agpgart-via 0000:00:00.0: AGP aperture is 128M @ 0xd0000000
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
via-rhine.c:v1.10-LK1.4.3 2007-03-06 Written by Donald Becker
via-rhine: Broken BIOS detected, avoid_D3 enabled.
via-rhine 0000:00:12.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
eth0: VIA Rhine II at 0xdfffd000, 00:16:17:df:67:79, IRQ 23.
eth0: MII PHY found at address 1, status 0x7849 advertising 01e1 Link 0000.
nvidiafb 0000:02:00.0: PCI INT A -> GSI 24 (level, low) -> IRQ 24
nvidiafb: Device ID: 10de0390
nvidiafb: CRTC0 analog not found
nvidiafb: CRTC1 analog not found
i2c-adapter i2c-1: unable to read EDID block.
i2c-adapter i2c-1: unable to read EDID block.
Linux video capture interface: v2.00
input: PC Speaker as /class/input/input4
saa7130/34: v4l2 driver version 0.2.14 loaded
i2c-adapter i2c-1: unable to read EDID block.
i2c-adapter i2c-2: unable to read EDID block.
input: X10 WTI RF receiver as /class/input/input5
ati_remote: Weird data, len=1 ff 01 00 00 00 00 ...
usbcore: registered new interface driver ati_remote
ati_remote: Registered USB driver ATI/X10 RF USB Remote Control v. 2.2.1
usblp0: USB Bidirectional printer dev 3 if 1 alt 0 proto 2 vid 0x04B8 pid 0x0806
i2c-adapter i2c-2: unable to read EDID block.
phy0 -> rt2500usb_init_eeprom: Error - Invalid RT chipset detected.
phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
usbcore: registered new interface driver rt2500usb
usbcore: registered new interface driver usblp
i2c-adapter i2c-2: unable to read EDID block.
nvidiafb: Unable to detect display type...
...Using default of CRT
nvidiafb: Unable to detect which CRTCNumber...
...Defaulting to CRTCNumber 0
nvidiafb: Using CRT on CRTC 0
nvidiafb: MTRR set to ON
fbcon: NV39 (fb0) is primary device
Console: switching to colour frame buffer device 80x30
nvidiafb: PCI nVidia NV39 framebuffer (64MB @ 0xC0000000)
HDA Intel 0000:04:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
HDA Intel 0000:04:01.0: setting latency timer to 64
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
saa7134 0000:07:09.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
saa7133[0]: found at 0000:07:09.0, rev: 209, irq: 16, latency: 32, mmio: 0xdf5ff000
saa7133[0]: subsystem: 16be:0010, board: Medion/Creatix CTX953 Hybrid [card=134,autodetected]
saa7133[0]: board init: gpio is 0
saa7133[0]: i2c eeprom 00: be 16 10 00 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
saa7133[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff 00 01 50 32 79 01 3c ca 50
saa7133[0]: i2c eeprom 20: 01 40 01 02 02 03 01 00 06 ff 00 2c 02 51 96 2b
saa7133[0]: i2c eeprom 30: a7 58 7a 1f 03 8e 84 5e da 7a 04 b3 05 87 b2 3c
saa7133[0]: i2c eeprom 40: ff 21 00 c0 96 10 03 22 15 00 fd 79 44 9f c2 8f
saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
tuner' 4-004b: chip found @ 0x96 (saa7133[0])
input: ImExPS/2 Generic Explorer Mouse as /class/input/input6
tda829x 4-004b: setting tuner address to 60
tda827x_attach: driver disabled by Kconfig
tda829x 4-004b: type set to tda8290+75a
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
tda827x_attach: driver disabled by Kconfig
saa7133[0]/dvb: no tda827x tuner found at addr: 60
phy1: Selected rate control algorithm 'pid'
usbcore: registered new interface driver rt73usb
eth0: link down
firmware: requesting rt73.bin

CPU info
Code:
processor   : 0
vendor_id   : GenuineIntel
cpu family   : 6
model      : 15
model name   : Intel(R) Core(TM)2 CPU          6300  @ 1.86GHz
stepping   : 6
cpu MHz      : 1861.935
cache size   : 2048 KB
physical id   : 0
siblings   : 2
core id      : 0
cpu cores   : 2
apicid      : 0
initial apicid   : 0
fdiv_bug   : no
hlt_bug      : no
f00f_bug   : no
coma_bug   : no
fpu      : yes
fpu_exception   : yes
cpuid level   : 10
wp      : yes
flags      : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm
bogomips   : 3723.87
clflush size   : 64
power management:

processor   : 1
vendor_id   : GenuineIntel
cpu family   : 6
model      : 15
model name   : Intel(R) Core(TM)2 CPU          6300  @ 1.86GHz
stepping   : 6
cpu MHz      : 1861.935
cache size   : 2048 KB
physical id   : 0
siblings   : 2
core id      : 1
cpu cores   : 2
apicid      : 1
initial apicid   : 1
fdiv_bug   : no
hlt_bug      : no
f00f_bug   : no
coma_bug   : no
fpu      : yes
fpu_exception   : yes
cpuid level   : 10
wp      : yes
flags      : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm
bogomips   : 3724.30
clflush size   : 64
power management:


dmesg
Code:

ror ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered
+------ PCI-Express Device Error ------+
Error Severity      : Uncorrected (Non-Fatal)
PCIE Bus Error type   : Transaction Layer
Flow Control Protocol    : First
Receiver ID      : 0010
VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h
pcieport-driver 0000:00:02.0: broadcast error_detected message
pcieport-driver 0000:00:02.0: broadcast mmio_enabled message
pcieport-driver 0000:00:02.0: broadcast resume message
pcieport-driver 0000:00:02.0: AER driver successfully recovered

xerrs.log
Code:
extention tar.z ignored

_________________
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch
Back to top
View user's profile Send private message 
big_bass

Joined: 13 Aug 2007
Posts: 1747

PostPosted: Tue 28 Apr 2009, 10:43    Post subject:  

Béèm

thanks for posting

with the information you posted
I was able to investigate

and that second drive you have has given
many people trouble in linux

and there were different approaches how to solve this

after weeding through a lot of techno jargon
what seems to me the easiest solution was

1.) Turn on AHCI in BIOS.

Probably you got "Standard-IDE" or similar selected in the BIOS IDE Setup.
Toggle it to AHCI mode

look at VIA
http://linux-ata.org/driver-status.html

if you get lucky with that dance Laughing
=====================

plan B:
2.)adding to the kernel a APPEND

add this into your kernel lilo parameter line
Code:
APPEND  ide_generic.probe_mask=0x0


what happens using that is
using a mask of 0x0 will disable all ide probing

I don't use Grub on my box but grub doesn't
have a APPENED option like lilo

you would add ide_generic.probe_mask=0x0
to the kernel line as you would any other option you needed to pass
with grub

notice that your CD is listed a hda? now

well if all goes well it be will be

everything /dev/sd(a-z)
or cdroms /dev/sr(0-9)


-------------------------------------------------
looking over the other info SMP is working fine
and was detected correctly



big_bass

_________________
debian wheezy ,linux mint, slackware I use them all and they all have good points
Mint would be best for general users though

Last edited by big_bass on Wed 13 May 2009, 10:48; edited 2 times in total
Back to top
View user's profile Send private message 
big_bass

Joined: 13 Aug 2007
Posts: 1747

PostPosted: Tue 28 Apr 2009, 12:50    Post subject:  

progress report

the problem I had with booting USB
turned out to be a blessing


I boot live CD in RAM

my USB gets detected

I dont use a save file

I just save what I want to USB flash

since I have 2GB RAM
I can work all day flushing the cache
and zero problems with layers

I can switch out different USB flash devices
if I had to do a major backup of info

In fact I built the Slaxer_Pup iso
completely running from RAM

nice when things dont work as expected Very Happy



I used to use USB boot as my standard install
which worked nicely on all puppy versions since 216

but when I tried to build woof USB I ran out of RAM
and it was very difficult at first to figure out what was going on

but now I have a great work around for that

big_bass

_________________
debian wheezy ,linux mint, slackware I use them all and they all have good points
Mint would be best for general users though
Back to top
View user's profile Send private message 
Béèm


Joined: 21 Nov 2006
Posts: 11782
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win

PostPosted: Tue 28 Apr 2009, 14:10    Post subject:  

@big_bass,
Thank you for investigating.
I should have mentioned I already went to your point one.
Nor setting to AHCI or RAID for the VIA controller is an option, as Windows won't load anymore.

I will try your interesting plan B and report back.

However, any woof distro like upup with kernel 2.6.29.1 solves the problem also. Maybe this kernel is extended with support for the VIA controller in IDE mode.

EDIT
No joy with the APPEND parameter, but it was worth the try.
The first HDD is still sda.

_________________
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch
Back to top
View user's profile Send private message 
big_bass

Joined: 13 Aug 2007
Posts: 1747

PostPosted: Tue 28 Apr 2009, 21:53    Post subject:  

Béèm

thanks for testing and posting the info
you might be surprised with a fix for
that drive

but for now find a kernel that locates it for you

the most important thing here is I will have a list of working
hardware and hardware that isnt detected

leading to better service for more people

I wont be switching out kernels this kernel is used
by 10 's of thousands of users world wide I just need to make some tweeks
for puppy but its looking really good
I know there is a lot

of changes going on in puppy
I just want to keep puppy updated
and stable

thank you
some have PM.d me with thier reports
but more people can help if you post the .gzipped reports here

big_bass

_________________
debian wheezy ,linux mint, slackware I use them all and they all have good points
Mint would be best for general users though
Back to top
View user's profile Send private message 
EZ4arabs

Joined: 19 Jul 2006
Posts: 84

PostPosted: Sat 02 May 2009, 04:15    Post subject:  

Thank you big_bass for sharing your creation.

01micko wrote:
big_bass
............Ok, wireless. I have a Netgear WG511V2 pcmcia card on this one... crappy Marvell chipset unsupported by Linux... however it works a treat in all Puppies with ndiswrapper. This is where I hit a snag. Crying or Very sad . All seemed to be going ok when I got a fatal error.... no ndiswrapper module! Please load another module!..........
Mick


I got the same error too and I might be wrong as am still learning but I couldn't find ndiswrapper.ko .can you please big_bass complie that module.

also my lucent modem was not detected and in other puppy versions martian modem works well but when I tried:
modprobe martian_dev
the error was module not found . also there are no ltserial ,ltmodem,agerserial modules.
can you please complie martian module and how to mknod for the /dev/ttySM0 device too if its not too much trouble.

other than that it works well.
Thank you.
Back to top
View user's profile Send private message 
Béèm


Joined: 21 Nov 2006
Posts: 11782
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win

PostPosted: Sat 02 May 2009, 15:36    Post subject:  

I didn't had time to post the info requested by Big_Bass
Here goes.
Xorg.0.log.gz
Description 
gz

 Download 
Filename  Xorg.0.log.gz 
Filesize  6.63 KB 
Downloaded  340 Time(s) 
xerrs.log.gz
Description 
gz

 Download 
Filename  xerrs.log.gz 
Filesize  895 Bytes 
Downloaded  366 Time(s) 
dmesg.txt.gz
Description 
gz

 Download 
Filename  dmesg.txt.gz 
Filesize  383 Bytes 
Downloaded  344 Time(s) 
cpuinfo.txt.gz
Description 
gz

 Download 
Filename  cpuinfo.txt.gz 
Filesize  477 Bytes 
Downloaded  333 Time(s) 
bootkernel.log.gz
Description 
gz

 Download 
Filename  bootkernel.log.gz 
Filesize  5.22 KB 
Downloaded  341 Time(s) 

_________________
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch
Back to top
View user's profile Send private message 
pakt


Joined: 04 Jun 2005
Posts: 1089
Location: Sweden

PostPosted: Mon 04 May 2009, 06:22    Post subject:  

OK, had a chance to test SlaxerPup on my oldest laptop: a PII, 300MHz Dell Latitude, and am happy to report that all hardware (that I've tested) works!

There is no built-in network interface in this laptop so I'm using an Atmel-based PCMCIA wifi card. I had to load the 'atmel-cs' driver before I could use the network wizard to configure wifi (I'm writing this using SlaxerPup on the D300XT while listening to CURTIN FM streaming through gxine. Amazing how well SlaxerPup works on this old Pentium II laptop from the last century Very Happy)

There is only one USB port (USB 1.0) on this machine, so I've connected a 4-port hub to share a USB mouse and a USB flash stick. Works fine. Wouldn't be able to boot through the USB port though. Don't know if I would be able to boot through a PCMCIA USB 2.0 adapter - that's something I got working in some older Puppy years ago by adding the cardbus driver to initrd.gz...

I've attached the 'info_get' tarball below. In case you wonder about the strange entry for the harddisk in dmesg ('hda: Hitachi XX.V.3.4.0.0, CFA DISK drive'), I've replaced the harddisk in this machine with an IDE-to-CF card adapter and a 1GB CF flash card. On that, I have a frugal install of Puppy 1.0.7 Wink

Paul

Edit: Forgot to mention, the laptop has only 128MB RAM. Running from CD with pfix=ram, there is still 55MB RAM free.
info_get_D300XT.tar.gz
Description 
gz

 Download 
Filename  info_get_D300XT.tar.gz 
Filesize  11.55 KB 
Downloaded  351 Time(s) 

_________________
Testing Puppy since v0.9.2 - my desktop OS since v1.0.7
Running SlaxerPup-4.12 - Puppy with a Slackware 12.2 heart Cool
Back to top
View user's profile Send private message 
big_bass

Joined: 13 Aug 2007
Posts: 1747

PostPosted: Tue 05 May 2009, 22:44    Post subject:  

Hey Paul (pakt)

thanks for posting your results

great report Cool


if you have any suggestions post here or PM me


Joe

_________________
debian wheezy ,linux mint, slackware I use them all and they all have good points
Mint would be best for general users though
Back to top
View user's profile Send private message 
big_bass

Joined: 13 Aug 2007
Posts: 1747

PostPosted: Tue 12 May 2009, 11:49    Post subject: pkgtools  

1.) imagine installing slackware packages the official way so what you learn today can be used for years to come
using official tools
you only need this

pkgtools updated 6/10/09 to add JWM and iceWM fixmenus
slackware pkgtools as a pet to install official slackware packages
see the very first post for correct links

image one
--------------------------------------------------------------------------------

UPDATED 5/25/09 to src2pkg 1.98

build your own packages from source!
......now for the brave adventurous types forum member "amigo" maintains src2pkg I setup the puppy base for it to work correctly
with slackware tools
image two
src2pkg-1.9.8-noarch-11.tgz

use pkgtools to install src2pkg then
only once you need to run in console
Code:
src2pkg --setup


-->it will compile on your machine 412 devx needs to be active

2.)imagine learning how to build slackware packages from source code even downloading directly from a URL and auto build it Very Happy

3.) now imagine leaning those professional skills in the comfortable
puppy environment surrounding you

4.)let's take the first step just a simple visual
slaxer install packages 1.png
 Description   
 Filesize   24.2 KB
 Viewed   1740 Time(s)

slaxer install packages 1.png

slaxer install packages 2.png
 Description   
 Filesize   9.21 KB
 Viewed   1745 Time(s)

slaxer install packages 2.png


_________________
debian wheezy ,linux mint, slackware I use them all and they all have good points
Mint would be best for general users though

Last edited by big_bass on Thu 08 Oct 2009, 12:03; edited 8 times in total
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 5 of 32 [470 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, ..., 30, 31, 32 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Cutting edge
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.2333s ][ Queries: 13 (0.0085s) ][ GZIP on ]