User Feedback :: log file location



Trying out DSL 4.2 on all the machines.  
I'll report on the wireless cards and adapters.

Could you point me to where DSL from live CD stores the log files?
dmesg is truncated, size limit I guess, and all I get is a lot of errors looking at the many card readers on new systems.  There is a reader and usb hubs on the box, monitor, and printer  they are all empty. I think they generate a lot of no disk errors.

Looked in the ramdisk for the log file but they are old.

I solved my wireless configuration problems moving from machine to machine with a linksys WGA54G.  It saves the wireless configuration and I just plug it into the ethernet jack.

Good work, I'll buy the book this month.

Thanks in advance

syslogd isn't running by default to save ram; it's one of the reasons to DSL's speed. So actually none log files get generated (they wouldn't be much use on a livecd anyway)..

A card reader shouldn't trigger a no disk error; in fact I doubt such error even exists in Linux :;):. Could you post the errors?

When you start dsl, add the syslog cheatcode.

Also, run dmesg instead of looking at the dmesg file.

OK thanks I'll try the syslog cheatcode to try and capture what's going on.
Not sure I understand about running dmesg.  It type dmesg in a console session and get about two screens of info from errors late in the boot sequence.

I was lured into DSL 4.2 for the sata feature as a unity feature between 2.1b "I think" DSL-N and DSL 3.2.  Anyway so far the wireless works better for me under 3.2.  The WMP55AG "atheros chip" works oob.  I can see ath0 in 4.2 with iwconfig but havn't got it to work.  My other machines have linksys with broadcom chips that work with ndiswrapper and bcmwl5.inf in 3.2 but no joy with 4.2.

The wireless game adapter is me work around.

I'll post the errors if I can capture them.  It's a long list but  all but wireless still works.
Thanks.

Quote
I'll post the errors if I can capture them.  It's a long list but  all but wireless still works.

Try:
# dmesg > ~/dmesg.log

That pipes it to a file in your home directory so you can edit, copy, paste, etc.

I got bcm43* marginally working in DSL 4+ but I have warnings related to "driver features might not be available." Those warnings are accurate!

Next Page...
original here.