The Debian-Live Daedalus Starter Kit

[rcrsn51]

In the PeasyWiFi config, have you set INTERFACE=wlan1?

[dcung]

In the PeasyWiFi config, have you set INTERFACE=wlan1?

Yes...

[rcrsn51]

Then set DRIVER=nl80211,wext

[dcung]

Then set DRIVER=nl80211,wext

Done. I tried WPA, WPA2...failed.
I saw few open network, probably some neighbour's...so I tried it and it connected.
At least, now the USB adapter 'works' I guess...
I'll try again later in the day and update if I got further progress....

pwf.conf

Code: Select all

export INTERFACE=wlan1
export DRIVER=nl80211,wext
export PROFILEPATH=/etc/pwf/wifi
export TRIES=5
export STATIC=""
export GATEWAY=""

[rcrsn51]

I have an adapter that uses this 88x2bu driver and it works for me. But I am connecting to an n-mode wifi router. WPA2 is the definite choice.

I once owned an ac-mode router and had much trouble connecting via Linux. So I got rid of it.

If you really want to use wifi, I would get a cheap n-mode adapter.

[dcung]

Rebooted.
And got it connected to both my 3G and 5G networks with WPA2....(WPA failed - prob my netgear configured to reject, I gotta check, I forgot).
Tried browsing, youtube....and works.

This is a cheap spare adapter that I don't usually use.
All my notebook/laptop sort of got its own working wifi.
Now I know I can use this spare in Dogs....Thanks Bill.

[rcrsn51]

Excellent. That's the first report I have seen of someone having good results with ac-mode.

Now I know I can use this spare in Dogs

Keep in mind that hardware drivers like this are kernel-specific. You can ONLY use them in an OS with the exact matching kernel.

Regarding nl80211: See the discussion on Page 9.

[rcrsn51]

Hi Fred: I ran some tests with my build-essential and linux-headers modules, activating them on-the-fly with both your loadmodule tool and mine.

Both methods worked OK. So there may not be a problem.

But it still feels safer to let overlayfs activate them at bootup.

[dcung]

The procedures for installing Nvidia drivers in the Starter Kit are described here (Post 664).

The advantage of Method B is that you can pre-make squashfs modules for the build-essential and linux-headers packages. The Nvidia installer will happily use them without requiring extra stuff. I occasionally have trouble activating such complicated modules using the new load-on-the-fly tools, so I prefer to put them in the 'live' folder of my Starter Kit install where they will auto-load at bootup.

I went to the Nvidia site and got the legacy-390.xx series package. I set up Method B and ran the mk-nvidia script. It worked smoothly.

On the next reboot, I was running the nvidia driver as expected.

Reading your experience, I revisited Dell D630 nvidia driver issue.
Hoping that since I have StretchDog, BionicDog and FossaDog on D630 laptop and all using nvidia driver v340, I tried again with Bullseye (round 2).
I tried (Method B) all 3 legacy packages, v304, v340, v390 - deleting change directory each time. No such luck for me. Reverted to VESA upon reboots.

BTW - I did pre-make squashfs modules for the build-essential and linux-headers packages, but I didn't use it. After putting it in live directory and saw them loaded during boot, just to check I re-run "apt-get update && apt-get install linux-headers-5.10.0-6-amd64" and it still get installed (again?). I was expecting to get "latest already installed" message, just like when I run the headers installation twice.

I used Apt2Sfs and it created linux-headers-5.10.0-6-amd64_build-essential.squashfs file (about 100MB).

So, I played safe and didn't use it. Prior to running mk-nvidia script each time, I deleted change dir and re-run
apt-get update
apt-get install linux-headers-$(uname -r)
apt-get install build-essential

[rcrsn51]

I suspect that the Nvidia v304 and v340 packages are not compatible with the Bullseye k5.10 kernel, and the v390 package might not recognize your card. The Nvidia web site has lists of supported devices for each driver package.

Did you try Method A with Bullseye on the Dell?

But I have also found Method B to sometimes be a crap-shoot. The advantage of Method A is that it will tell you in advance what should work.

Regarding activating a module versus installing the corresponding package: when you activate a module, it does NOT get registered into apt. So when you run apt, the system is unaware that the files are already present in the module and will install them anyway.

[dcung]

I suspect that the Nvidia v304 and v340 packages are not compatible with the Bullseye k5.10 kernel, and the v390 package might not recognize your card. The Nvidia web site has lists of supported devices for each driver package.

I think so too.

Did you try Method A with Bullseye on the Dell?

Yes. But v340 legacy not available in Bullseye repo.

I have updated the other thread. Dell D630 - BusterDog works with Method A. Does not work with Method B.
viewtopic.php?f=58&t=3062&p=27091#p27091

[rcrsn51]

I checked the Nvidia site. Your Quadro NVS 135M is NOT supported by the v390 driver. If we are correct that the older drivers won't work with a modern k5.10.x kernel, then your Dell won't work in Bullseye (unless you use nouveau).

[rcrsn51]

Here is my final question on the subject. My test Nvidia machine is a low-power Atom unit, but it has HDMI output. Can it drive a big-screen TV or do you need a separate graphics card to do that?

[dcung]

Here is my final question on the subject. My test Nvidia machine is a low-power Atom unit, but it has HDMI output. Can it drive a big-screen TV or do you need a separate graphics card to do that?

"Yes", provided your TV has HDMI input. You simply get a HDMI cable. No need separate graphics card.
Meaning that you will get picture on the TV, but whether you are happy with the resolution/performance is another question. My guess is that you won't be happy with video performance.

I have been using my Dell D630 since 2018 to drive 47in old TV. Started with BionicDog then change FossaDog with 1920x1080 on TV. Which meet my expectation ONLY with nVidia driver. CPU util hits the roof if you use nouveau. Nowadays, there's one TV channel that we watch daily, during commercials would send the CPU sky high. I have to lower the resolution and I don't like the look (i.e. ratio, people face, etc. looks funny.)

So, I put this Asus/E6750/7900GS instead. It looks bigger/uglier than the D630...but....it can drive 1920x1080 with no problem. CPU average 50-70% when playing full screen video. Else, even lower CPU... In fact, I like it better than my newer android smart TV as I can control with mini mouse/keyboard than a TV remote and response faster.

In the old forum, you can see my old posts when I was selecting which pup/dog to use. Basically it was xrandr command that behaviour in BionicDog/FossaDog that I couldn't replicate in others (for multi monitor).
But now, only TV screen and no laptop monitor to consider 'I can use any pup/dog' -> but turns out, only StretchDog works with my 7900GS nvidia. So, StretchDog it is, Bill...

So, in summary. Unless you're ok with 1024x768 or so resolution, you probably won't use the Atom. But then again HDMI cable is cheap. You may even have one already. Just plug it in and check if you like what you see.

I use one of these $10 to control.

[Clarity]

@rcrsn51 the single cable brings BOTH audio and video from the PC to the TV. Depending on which distro you use, it should/could work OOTB.

In fact, I have experienced a side benefit: I do not use glasses when working on this system. Not to mention that there's ONLY 1 wire + power cable on the PC: cable-free.

Enjoy

P.S. My TV is a smart-TV meaning it has internet ability beyond broadcast TV programming. Thus using the TV remote I can freely at any time switch from PC to broadcast to TV's internet whenever I wish. This TV has multiple HDMI ports alowing me to connect multiple PCs and other to the single TV to use at my discretion. The PCs continue to run with or without the active connection to the TV.

Mere notes of flexibility that you will find in its friendly use.

[TerryH]

Here is my final question on the subject. My test Nvidia machine is a low-power Atom unit, but it has HDMI output. Can it drive a big-screen TV or do you need a separate graphics card to do that?

I have a small mini pc with Z3735F Atom processor 2GB RAM, it worked fine when i had connected it to my 152CM (60") Samsung 4K TV.

[rcrsn51]

I have a small mini pc with Z3735F Atom processor 2GB RAM, it worked fine when i had connected it to my 152CM (60") Samsung 4K TV.

Thanks. Is that 3840x2160?

I have a little 19in TV that I have used successfully over HDMI with a variety of low-powered machines at 1366x768. I was curious about how much more horsepower it takes to get to the next level.

[TerryH]

I have a small mini pc with Z3735F Atom processor 2GB RAM, it worked fine when i had connected it to my 152CM (60") Samsung 4K TV.

Thanks. Is that 3840x2160?

I have a little 19in TV that I have used successfully over HDMI with a variety of low-powered machines at 1366x768. I was curious about how much more horsepower it takes to get to the next level.

Yes it is.

[dcung]

Here is my final question on the subject. My test Nvidia machine is a low-power Atom unit, but it has HDMI output. Can it drive a big-screen TV or do you need a separate graphics card to do that?

I have a small mini pc with Z3735F Atom processor 2GB RAM, it worked fine when i had connected it to my 152CM (60") Samsung 4K TV.

Right...I should have asked what Atom processor he has... My bad...I have ancient Atom mini laptop gathering dust...can't remember the model...

[dcung]

I checked the Nvidia site. Your Quadro NVS 135M is NOT supported by the v390 driver. If we are correct that the older drivers won't work with a modern k5.10.x kernel, then your Dell won't work in Bullseye (unless you use nouveau).

Yes. Last Quadro NVS 135M listed as supported was in v340 driver.

[rcrsn51]

FWIW, I compiled the Nvidia v390 driver for k5.10.0-6-amd64 and packaged the results as a squashfs module. I can then "install" the driver just by dropping the module into my Starter Kit "live" folder.

[rcrsn51]

CPUtemp v3.5 is posted below with some updates to the Info section.

The handy cpu-x CPU information tool is now available directly from the Bullseye repo.

--------------------------

[rcrsn51]

This version adds an Info button. It uses the ffprobe tool to display information about a file.

This is important if you want to join some media files together, where the input files must have identical characteristics.
For example, to standardize an MP3 file, use the ANY-ANY method and a Config line like:

Code: Select all

export ANYOPTS="-ab 128k -ar 44100 -sample_fmt s16p -ac 2"

Be aware that ffmpeg sometimes has trouble with complicated filenames that contain non-standard characters. You will get a "File not found" message. If necessary, simplify the filename. Debug mode will be helpful here. In your Config, set the DEBUG variable to "yes".

V2.3.6 has some improvements to the ANY-ANY method that will be useful in batch processing. You can now make selections like ANY-MP3. If the program does not have a predefined rule for doing the conversion, like with ANY-OGG, it can use the optional OTHEROPTS variable.

The same procedure works with obscure formats that are not in the From list.

If a video clip has no audio track, you can add a silent track using the ANY-ANY method and this ANYOPTS variable:

Code: Select all

export ANYOPTS="-f lavfi -i anullsrc -acodec aac -vcodec copy -shortest"

To change the audio track, use:

Code: Select all

export ANYOPTS="-i /path/to/new-audio-file -map 0:v:0 -map 1:a:0 -acodec aac -vcodec copy -shortest"

To extract the audio track from any video file, use:

Code: Select all

export ANYOPTS="-vn -acodec copy"

To reduce the audio track from stereo to mono, use:

Code: Select all

export ANYOPTS="-ac 1"

To shrink a hi-def MTS camcorder video to a smaller MP4, use:

Code: Select all

export MP4OPTS="-vf scale=320:240"

V1.10 now supports DVD-compatible .vob files You can convert a variety of video formats to VOB. Look for the VOBOPTS variable in the Config. It has several variations depending on the target video hardware.

------------------------

Read here for more examples.

------------------

[rcrsn51]

Audio Converter updated to v1.8 above .

[fredx181]

Hi Bill, I downloaded your Bullseye Starter Kit from Mediafire and was very slow, took me around 1 hour.
I've mirrored it on Github:
https://github.com/DebianDog/MakeLive/r ... md64-6.iso (takes for me 25 seconds to download )
Will try to update anytime in case you update it.

Fred

[rcrsn51]

Thanks. I can get the ISO from Mediafire in 4 minutes, about the same time as from github.

[fredx181]

Thanks. I can get the ISO from Mediafire in 4 minutes, about the same time as from github.

Ok, maybe it has to do with my location or/and time of day that it was so slow for me from MediaFire.

[rcrsn51]

I have added a link to the github download on the main Page 1 post.

[rcrsn51]

The post here discusses how to boot mainstream Linuxes directly from their ISO files. The technique can also be used with the Starter Kit and other Porteus-style ISOs.

Code: Select all

menuentry "DebLive_Bullseye-amd64-6 ISO boot" {
  set isofile="/BigBoy/DebLive_Bullseye-amd64-6.iso"
  set uuid="0db94719-cdf1-44b7-9766-23db62fb85a5"
  search --no-floppy --fs-uuid --set=root $uuid
  loopback loop $isofile
  set root=(loop)
  linux (loop)/live/vmlinuz1 edd=off noauto copy2ram from=UUID:$uuid/$isofile
  initrd (loop)/live/initrd1.xz
}

Thank you to gyrog for testing this.

---------------------

[rcrsn51]

The DebLive Multi Installer has been updated here.